Evolved Multimedia Broadcast/Multicast Service (EMBMS) System and EMBMS System Management Method

ABSTRACT

Embodiments of the present disclosure provide an eMBMS system that includes a GW-C device connected to a mobility management entity and broadcast/multicast service center and a GW-U device connected to a base station and the mobility management entity. The GW-C device is configured to perform core network signaling interaction with the broadcast/multicast service center and the mobility management entity, and to send a forwarding indication message to the GW-U device. The GW-U device is configured to receive signaling from the base station and send the signaling to the GW-C device according to the forwarding indication message. The GW-C device is further configured to receive and process the signaling from the GW-U device. The GW-U device is further configured to send a received broadcast/multicast service data packet to the base station according to the forwarding indication message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2015/083358, filed on Jul. 6, 2015, the disclosure of which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to the computer field, and in particular,to an evolved multimedia broadcast/multicast service (eMBMS) system andan eMBMS system management method.

BACKGROUND

A logical architecture of an existing eMBMS system is shown in FIG. 1and includes an evolved NodeB (eNB), a multi-cell/multicast coordinationentity (MCE), a mobility management entity (MME), an MBMS gateway(MBMS-GW), and a broadcast/multicast service center (BM-SC). The eNBconnects to the MBMS-GW using an M1 interface, the eNB connects to theMCE using an M2 interface, the MCE connects to the MME using an M3interface, the MME connects to the MBMS-GW using an Sm interface, andthe MBMS-GW connects to the BM-SC using a SGmb interface and an SGi-mbinterface.

The MBMS-GW in this system has both a control plane function and a userplane function. The control plane function is responsible for receivingand processing session control signaling of an MBMS bearer service fromthe BM-SC and necessary information provided by the gateway user planefunction, and for performing signaling interaction with the eNB.

The gateway user plane function is responsible for transiting signalingbetween the BM-SC and the control plane function, receiving abroadcast/multicast service data packet from the BM-SC, and sending thebroadcast/multicast service data packet to the eNB.

However, with network evolution and service innovation, when a newfunction is added into or a new service is deployed in a control planeof the MBMS-GW, a forwarding plane may need to be modified. This mayincrease modification costs and is not conducive to new servicedeployment.

SUMMARY

The present disclosure provides an eMBMS system and an eMBMS systemmanagement method. Embodiments of the present disclosure may allow acontrol plane function and a forwarding plane function of an MBMS-GW toevolve independently.

In some embodiments, to achieve the foregoing objectives, the followingtechnical solutions are adopted in the present disclosure.

According to a first aspect, an eMBMS system is provided and includes abroadcast/multicast service center, a base station, a mobilitymanagement entity connected to the base station, a gateway control plane(GW-C) device connected to the mobility management entity and thebroadcast/multicast service center, and a gateway user plane (GW-U)device connected to the base station and the broadcast/multicast servicecenter. The GW-C device connects to the GW-U device. The GW-C device isconfigured to perform core network signaling interaction with thebroadcast/multicast service center and the mobility management entityand send a forwarding indication message to the GW-U device. Theforwarding indication message is for instructing the GW-U device toprocess a packet received by the GW-U device. The GW-U device isconfigured to receive signaling sent by the base station and send thesignaling to the GW-C device according to the forwarding indicationmessage. The GW-C device is further configured to receive and processthe signaling sent by the GW-U device. The GW-U device is furtherconfigured to, in a data transmission procedure, receive abroadcast/multicast service data packet sent by the broadcast/multicastservice center and send the broadcast/multicast service data packet tothe base station according to the forwarding indication message.

In a first possible implementation of the first aspect, the GW-C deviceis configured to, in a session establishment procedure, receive a firstsession start request message sent by the broadcast/multicast servicecenter and send a second session start request message to the mobilitymanagement entity. The first session start request message is forestablishing a bearer between the GW-U device and thebroadcast/multicast service center, and the second session start requestmessage is for establishing a bearer between the base station and theGW-U device.

With reference to the first aspect or the first possible implementationof the first aspect, in a second possible implementation, the GW-Udevice connects to the broadcast/multicast service center using anSGi-mb interface, and the GW-C device is further configured to allocate,when a sending manner on the SGi-mb interface is a unicast manner, adestination User Datagram Protocol (UDP) port corresponding to theSGi-mb interface.

With reference to any possible implementation of the first aspect, orthe first to the second possible implementations of the first aspect, ina third possible implementation, the GW-U device connects to thebroadcast/multicast service center using an SGi-mb interface, and theGW-C device is further configured to send, when a sending manner on theSGi-mb interface is a multicast manner, a multicast group joininstruction message to the GW-U device. The multicast group joininstruction message includes a first multicast group join requestmessage, and is for instructing the GW-U device to send the firstmulticast group join request message to the broadcast/multicast servicecenter. The GW-U device is further configured to send the firstmulticast group join request message to the broadcast/multicast servicecenter. The broadcast/multicast service center is configured to add,according to the first multicast group join request message, the GW-Udevice into an IP multicast group using the broadcast/multicast servicecenter as a source point.

With reference to any possible implementation of the first aspect, orthe first to the third possible implementations of the first aspect, ina fourth possible implementation, the GW-U device connects to the basestation using an M1 interface, and the GW-C device is further configuredto allocate an IP multicast address of the M1 interface and a tunnelidentifier. The IP multicast address is for identifying an IP multicastgroup using the GW-U device as a source point.

With reference to any possible implementation of the first aspect, orthe first to the fourth possible implementations of the first aspect, ina fifth possible implementation, the forwarding indication messageincludes a first forwarding rule, and the first forwarding rule is arule used when the GW-U device processes the signaling sent by the basestation to the GW-U device. The GW-U device is configured to receive asecond multicast group join request message sent by the base station,preprocess the second multicast group join request message according tothe first forwarding rule, and send a preprocessed second multicastgroup join request message to the GW-C device. The GW-C device isfurther configured to add. after receiving the preprocessed secondmulticast group join request message and according to the preprocessedsecond multicast group join request message, the base station into theIP multicast group using the GW-U device as the source point.

With reference to any possible implementation of the first aspect, orthe first to the fifth possible implementations of the first aspect, ina sixth possible implementation, the forwarding indication messageincludes a second forwarding rule, and the second forwarding rule is arule used when the GW-U device processes the packet sent by thebroadcast/multicast service center to the GW-U device. The GW-U deviceis configured to, in the data transmission procedure, receive thebroadcast/multicast service data packet sent by the broadcast/multicastservice center, and send the broadcast/multicast service data packet tothe base station according to the second forwarding rule.

With reference to any possible implementation of the first aspect, orthe first to the sixth possible implementations of the first aspect, ina seventh possible implementation, the GW-C device is configured to, ina session termination procedure, receive a first session terminationrequest message sent by the broadcast/multicast service center, thefirst session termination request message including specified timeinformation, and release a bearer context at a moment specified by thespecified time information.

With reference to any possible implementation of the first aspect, orthe first to the seventh possible implementations of the first aspect,in an eighth possible implementation, the GW-C device is configured tosend the forwarding indication message to the GW-U device at the momentspecified by the specified time information. The forwarding indicationmessage includes a rule deletion instruction. The GW-U device is furtherconfigured to delete, according to the rule deletion instruction, asecond forwarding rule used when the GW-U device processes thebroadcast/multicast service data packet.

With reference to any possible implementation of the first aspect, orthe first to the eighth possible implementations of the first aspect, ina ninth possible implementation, the GW-C device is further configuredto send a second session termination request message to the mobilitymanagement entity. The second session termination request messageincludes the specified time information, such that the mobilitymanagement entity sends the specified time information to the basestation and the base station releases the bearer context according tothe specified time information.

With reference to any possible implementation of the first aspect, orthe first to the ninth possible implementations of the first aspect, ina tenth possible implementation, the GW-U device is further configuredto receive a first multicast group removal request message sent by thebase station, preprocess the first multicast group removal requestmessage according to a first forwarding rule of the GW-U device, andsend a preprocessed first multicast group removal request message to theGW-C device The GW-C device is further configured to remove, afterreceiving the preprocessed first multicast group removal request messageand according to the preprocessed first multicast group removal requestmessage, the base station from the IP multicast group using the GW-Udevice as the source point.

With reference to any possible implementation of the first aspect, orthe first to the tenth possible implementations of the first aspect, inan eleventh possible implementation, if the sending manner on the SGi-mbinterface between the broadcast/multicast service center and the gatewayuser plane device is the multicast manner, the GW-C device is furtherconfigured to send a multicast group removal instruction message to theGW-U device. The multicast group removal instruction message includes asecond multicast group removal request message and is for instructingthe GW-U device to send the second multicast group removal requestmessage to the broadcast/multicast service center The GW-U device isfurther configured to send the second multicast group removal requestmessage to the broadcast/multicast service center. The second multicastgroup removal request message is for instructing the broadcast/multicastservice center to remove the GW-U device from the IP multicast groupusing the broadcast/multicast service center as the source point.

According to a second aspect, an eMBMS system management method isapplied to an eMBMS system, where the eMBMS system includes abroadcast/multicast service center, a base station, a mobilitymanagement entity connected to the base station, a GW-C device connectedto the mobility management entity and the broadcast/multicast servicecenter, and a GW-U device connected to the base station and thebroadcast/multicast service center. The GW-C device connects to the GW-Udevice. The method includes performing, by the GW-C device, core networksignaling interaction with the broadcast/multicast service center andthe mobility management entity and sending, by the GW-C device, aforwarding indication message to the GW-U device. The forwardingindication message is for instructing the GW-U device to process apacket received by the GW-U device The method further includesreceiving, by the GW-U device, signaling sent by the base station andsending the signaling to the GW-C device according to the forwardingindication message. The method further includes receiving andprocessing, by the GW-C device, the signaling sent by the GW-U device.The method further includes, in a data transmission procedure,receiving, by the GW-U device, a broadcast/multicast service data packetsent by the broadcast/multicast service center, and sending thebroadcast/multicast service data packet to the base station according tothe forwarding indication message.

In a first possible implementation of the second aspect, the performing,by the GW-C device, core network signaling interaction with thebroadcast/multicast service center and the mobility management entityincludes, in a session establishment procedure, receiving, by the GW-Cdevice, a first session start request message sent by thebroadcast/multicast service center and sending, by the GW-C device, asecond session start request message to the mobility management entity.The first session start request message is for establishing a bearerbetween the GW-U device and the broadcast/multicast service center, andthe second session start request message is for establishing a bearerbetween the base station and the GW-U device.

With reference to the second aspect or the first possible implementationof the second aspect, in a second possible implementation, the GW-Udevice connects to the broadcast/multicast service center using anSGi-mb interface, and the method further includes allocating, when asending manner on the SGi-mb interface is a unicast manner, by the GW-Cdevice a destination UDP port corresponding to the SGi-mb interface.

With reference to any possible implementation of the second aspect, orthe first to the second possible implementations of the second aspect,in a third possible implementation, the GW-U device connects to thebroadcast/multicast service center using an SGi-mb interface, and themethod further includes sending, when a sending manner on the SGi-mbinterface is a multicast manner, by the GW-C device a multicast groupjoin instruction message to the GW-U device. The multicast group joininstruction message includes a first multicast group join requestmessage and is for instructing the GW-U device to send the firstmulticast group join request message to the broadcast/multicast servicecenter. The method further includes sending, by the GW-U device, thefirst multicast group join request message to the broadcast/multicastservice center and adding, by the broadcast/multicast service centeraccording to the first multicast group join request message, the GW-Udevice into an IP multicast group using the broadcast/multicast servicecenter as a source point.

With reference to any possible implementation of the second aspect, orthe first to the third possible implementations of the second aspect, ina fourth possible implementation, the GW-U device connects to the basestation using an M1 interface, and the method further includesallocating, by the GW-C device, an IP multicast address of the M1interface and a tunnel identifier. The IP multicast address is foridentifying an IP multicast group using the GW-U device as a sourcepoint.

With reference to any possible implementation of the second aspect, orthe first to the fourth possible implementations of the second aspect,in a fifth possible implementation, the forwarding indication messageincludes a first forwarding rule. The first forwarding rule is used whenthe GW-U device processes the signaling sent by the base station to theGW-U device. Receiving, by the GW-U device, signaling sent by the basestation, and sending the signaling to the GW-C device according to theforwarding indication message includes receiving, by the GW-U device, asecond multicast group join request message sent by the base station,preprocessing the second multicast group join request message accordingto the first forwarding rule, and sending a preprocessed secondmulticast group join request message to the GW-C device. Receiving andprocessing, by the GW-C device, the signaling sent by the GW-U deviceincludes adding, after receiving the preprocessed second multicast groupjoin request message, by the GW-C device according to the preprocessedsecond multicast group join request message, the base station into theIP multicast group using the GW-U device as the source point.

With reference to any possible implementation of the second aspect, orthe first to the fifth possible implementations of the second aspect, ina sixth possible implementation, the forwarding indication messageincludes a second forwarding rule. The second forwarding rule is usedwhen the GW-U device processes the packet sent by thebroadcast/multicast service center to the GW-U device. Sending, by theGW-U device, the broadcast/multicast service data packet to the basestation according to the forwarding indication message includes sending,by the GW-U device, the broadcast/multicast service data packet to thebase station according to the second forwarding rule.

With reference to any possible implementation of the second aspect, orthe first to the sixth possible implementations of the second aspect, ina seventh possible implementation, performing, by the GW-C device, corenetwork signaling interaction with the broadcast/multicast servicecenter includes, in a session termination procedure, receiving by theGW-C device a first session termination request message sent by thebroadcast/multicast service center, the first session terminationrequest message including specified time information, and releasing bythe GW-C device a bearer context at a moment specified by the specifiedtime information.

With reference to any possible implementation of the second aspect, orthe first to the seventh possible implementations of the second aspect,in an eighth possible implementation, sending, by the GW-C device, aforwarding indication message to the GW-U device includes sending by theGW-C device the forwarding indication message to the GW-U device at themoment specified by the specified time information. The forwardingindication message includes a rule deletion instruction. The methodfurther includes deleting, by the GW-U device according to the ruledeletion instruction, a second forwarding rule used when the GW-U deviceprocesses the broadcast/multicast service data packet.

With reference to any possible implementation of the second aspect, orthe first to the eighth possible implementations of the second aspect,in a ninth possible implementation, performing, by the GW-C device, corenetwork signaling interaction with the mobility management entityincludes sending, by the GW-C device, a second session terminationrequest message to the mobility management entity. The second sessiontermination request message includes the specified time information,such that the mobility management entity sends the specified timeinformation to the base station, and the base station releases thebearer context according to the specified time information.

With reference to any possible implementation of the second aspect, orthe first to the ninth possible implementations of the second aspect, ina tenth possible implementation, receiving, by the GW-U device,signaling sent by the base station, and sending the signaling to theGW-C device according to the first forwarding rule includes receiving,by the GW-U device, a first multicast group removal request message sentby the base station, preprocessing the first multicast group removalrequest message according to a first forwarding rule of the GW-U device,and sending a preprocessed first multicast group removal request messageto the GW-C device Receiving and processing, by the GW-C device, thesignaling includes removing, after receiving the preprocessed firstmulticast group removal request message, by the GW-C device according tothe preprocessed first multicast group removal request message, the basestation from the IP multicast group using the GW-U device as the sourcepoint.

With reference to any possible implementation of the second aspect, orthe first to the tenth possible implementations of the second aspect, inan eleventh possible implementation, if the sending manner on the SGi-mbinterface between the broadcast/multicast service center and the gatewayuser plane device is the multicast manner, the method further includessending a multicast group removal instruction message to the GW-Udevice. The multicast group removal instruction message includes asecond multicast group removal request message and is for instructingthe GW-U device to send the second multicast group removal requestmessage to the broadcast/multicast service center. The method furtherincludes sending, by the GW-U device, the second multicast group removalrequest message to the broadcast/multicast service center. The secondmulticast group removal request message is for instructing thebroadcast/multicast service center to remove the GW-U device from the IPmulticast group using the broadcast/multicast service center as thesource point.

According to a third aspect, an eMBMS system management method includesperforming, by a GW-C device, core network signaling interaction with abroadcast/multicast service center and a mobility management entity andsending a forwarding indication message to a GW-U device. The forwardingindication message is for instructing the GW-U device to process apacket received by the GW-U device. The method further includesreceiving and processing signaling sent by the GW-U device according tothe forwarding indication message. The signaling is sent by the basestation to the GW-U device.

In a first possible implementation of the third aspect, performing, bythe GW-C device, core network signaling interaction with abroadcast/multicast service center and a mobility management entityincludes, in a session establishment procedure, receiving a firstsession start request message sent by the broadcast/multicast servicecenter and sending a second session start request message to themobility management entity. The first session start request message isfor establishing a bearer between the GW-U device and thebroadcast/multicast service center, and the second session start requestmessage is for establishing a bearer between the base station and theGW-U device.

With reference to the third aspect or the first possible implementationof the third aspect, in a second possible implementation, the GW-Udevice connects to the broadcast/multicast service center using anSGi-mb interface, and the method further includes allocating, when asending manner on the SGi-mb interface is a unicast manner, adestination UDP port corresponding to the SGi-mb interface.

With reference to any possible implementation of the third aspect, orthe first to the second possible implementations of the third aspect, ina third possible implementation, the GW-U device connects to thebroadcast/multicast service center using an SGi-mb interface, and themethod further includes sending, when a sending manner on the SGi-mbinterface is a multicast manner, a multicast group join instructionmessage to the GW-U device. The multicast group join instruction messageincludes a first multicast group join request message and is forinstructing the GW-U device to send the first multicast group joinrequest message to the broadcast/multicast service center.

With reference to any possible implementation of the third aspect, orthe first to the third possible implementations of the third aspect, ina fourth possible implementation, the GW-U device connects to the basestation using an M1 interface, and the method further includesallocating an IP multicast address of the M1 interface and a tunnelidentifier. The IP multicast address is for identifying an IP multicastgroup using the GW-U device as a source point.

With reference to any possible implementation of the third aspect, orthe first to the fourth possible implementations of the third aspect, ina fifth possible implementation, the forwarding indication messageincludes a first forwarding rule, and the first forwarding rule is usedwhen the GW-U device processes the signaling sent by the base station tothe GW-U device. Receiving and processing signaling sent by the GW-Udevice according to the forwarding indication message includes receivinga preprocessed second multicast group join request message sent by theGW-U device. The preprocessed second multicast group join requestmessage is obtained after the GW-U device preprocesses, according to thefirst forwarding rule, a second multicast group join request messagesent by the base station. Receiving and processing signaling sent by theGW-U device according to the forwarding indication message furtherincludes adding, according to the preprocessed second multicast groupjoin request message, the base station into the IP multicast group usingthe GW-U device as the source point.

With reference to any possible implementation of the third aspect, orthe first to the fifth possible implementations of the third aspect, ina sixth possible implementation, performing, by the GW-C device, corenetwork signaling interaction with a broadcast/multicast service centerincludes, in a session termination procedure, receiving a first sessiontermination request message sent by the broadcast/multicast servicecenter, the first session termination request message includingspecified time information, and releasing a bearer context at a momentspecified by the specified time information.

With reference to any possible implementation of the third aspect, orthe first to the sixth possible implementations of the third aspect, ina seventh possible implementation, sending a forwarding indicationmessage to the GW-U device includes sending the forwarding indicationmessage to the GW-U device at the moment specified by the specified timeinformation. The forwarding indication message includes a rule deletioninstruction, such that the GW-U device deletes, according to the ruledeletion instruction, a second forwarding rule used when the GW-U deviceprocesses a broadcast/multicast service data packet.

With reference to any possible implementation of the third aspect, orthe first to the seventh possible implementations of the third aspect,in an eighth possible implementation, performing, by the GW-C device,core network signaling interaction with a mobility management entityincludes sending a second session termination request message to themobility management entity. The second session termination requestmessage includes the specified time information, such that the mobilitymanagement entity sends the specified time information to the basestation, and the base station releases the bearer context according tothe specified time information.

With reference to any possible implementation of the third aspect, orthe first to the eighth possible implementations of the third aspect, ina ninth possible implementation, receiving and processing signaling sentby the GW-U device according to the forwarding indication messageincludes receiving a preprocessed first multicast group removal requestmessage. The preprocessed first multicast group removal request messageis obtained after the GW-U device preprocesses, according to a firstforwarding rule, a first multicast group removal request message sent bythe base station. Receiving and processing signaling sent by the GW-Udevice according to the forwarding indication message further includesremoving, according to the preprocessed first multicast group removalrequest message, the base station from the IP multicast group using theGW-U device as the source point.

With reference to any possible implementation of the third aspect, orthe first to the ninth possible implementations of the third aspect, ina tenth possible implementation, if the sending manner on the SGi-mbinterface between the broadcast/multicast service center and the gatewayuser plane device is the multicast manner, the method further includessending a multicast group removal instruction message to the GW-Udevice. The multicast group removal instruction message includes asecond multicast group removal request message and is for instructingthe GW-U device to send the second multicast group removal requestmessage to the broadcast/multicast service center. The second multicastgroup removal request message is for instructing the broadcast/multicastservice center to remove the GW-U device from an IP multicast groupusing the broadcast/multicast service center as a source point.

According to a fourth aspect, a GW-C device includes a first interactionunit, a second interaction unit, and a third interaction unit. The firstinteraction unit is configured to perform core network signalinginteraction with a broadcast/multicast service center. The secondinteraction unit is configured to perform core network signalinginteraction with a mobility management entity. The third interactionunit is configured to send a forwarding indication message to a gatewayuser plane GW-U device. The forwarding indication message is forinstructing the GW-U device to process a packet received by the GW-Udevice. The third interaction unit is further configured to receive andprocess signaling sent by the GW-U device according to the forwardingindication message. The signaling is sent by the base station to theGW-U device.

In a first possible implementation of the fourth aspect, the firstinteraction unit is configured to receive, in a session establishmentprocedure, a first session start request message sent by thebroadcast/multicast service center, and the second interaction unit isconfigured to send a second session start request message to themobility management entity. The first session start request message isfor establishing a bearer between the GW-U device and thebroadcast/multicast service center, and the second session start requestmessage is for establishing a bearer between the base station and theGW-U device.

With reference to the fourth aspect or the first possible implementationof the fourth aspect, in a second possible implementation, the GW-Udevice connects to the broadcast/multicast service center using anSGi-mb interface, and the GW-C device further includes an allocationunit configured to allocate, when a sending manner on the SGi-mbinterface is a unicast manner, a destination UDP port corresponding tothe SGi-mb interface.

With reference to any possible implementation of the fourth aspect, orthe first to the second possible implementations of the fourth aspect,in a third possible implementation, the GW-U device connects to thebroadcast/multicast service center using an SGi-mb interface, and thethird interaction unit is further configured to send, when a sendingmanner on the SGi-mb interface is a multicast manner, a multicast groupjoin instruction message to the GW-U device. The multicast group joininstruction message includes a first multicast group join requestmessage and is for instructing the GW-U device to send the firstmulticast group join request message to the broadcast/multicast servicecenter.

With reference to any possible implementation of the fourth aspect, orthe first to the third possible implementations of the fourth aspect, ina fourth possible implementation, the GW-U device connects to the basestation using an M1 interface, and the allocation unit is configured toallocate an IP multicast address of the M1 interface and a tunnelidentifier. The IP multicast address is for identifying an IP multicastgroup using the GW-U device as a source point.

With reference to any possible implementation of the fourth aspect, orthe first to the fourth possible implementations of the fourth aspect,in a fifth possible implementation, the forwarding indication messageincludes a first forwarding rule, and the first forwarding rule is usedwhen the GW-U device processes the signaling sent by the base station tothe GW-U device. The third interaction unit is configured to receive apreprocessed second multicast group join request message sent by theGW-U device. The preprocessed second multicast group join requestmessage is obtained after the GW-U device preprocesses, according to thefirst forwarding rule, a second multicast group join request messagesent by the base station. The GW-C device further includes a multicastmanagement unit configured to add, according to the preprocessed secondmulticast group join request message, the base station into the IPmulticast group using the GW-U device as the source point.

With reference to any possible implementation of the fourth aspect, orthe first to the fifth possible implementations of the fourth aspect, ina sixth possible implementation, the first interaction unit is furtherconfigured to receive, in a session termination procedure, a firstsession termination request message sent by the broadcast/multicastservice center. The first session termination request message includesspecified time information. The GW-C device further includes a bearerrelease unit configured to release a bearer context at a momentspecified by the specified time information.

With reference to any possible implementation of the fourth aspect, orthe first to the sixth possible implementations of the fourth aspect, ina seventh possible implementation, the third interaction unit isconfigured to send the forwarding indication message to the GW-U deviceat the moment specified by the specified time information. Theforwarding indication message includes a rule deletion instruction, suchthat the GW-U device deletes, according to the rule deletioninstruction, a second forwarding rule used when the GW-U deviceprocesses a broadcast/multicast service data packet.

With reference to any possible implementation of the fourth aspect, orthe first to the seventh possible implementations of the fourth aspect,in an eighth possible implementation, the second interaction unit isfurther configured to send a second session termination request messageto the mobility management entity. The second session terminationrequest message includes the specified time information, such that themobility management entity sends the specified time information to thebase station, and the base station releases the bearer context accordingto the specified time information.

With reference to any possible implementation of the fourth aspect, orthe first to the ninth possible implementations of the fourth aspect, ina tenth possible implementation, the third interaction unit is furtherconfigured to receive a preprocessed first multicast group removalrequest message. The preprocessed first multicast group removal requestmessage is obtained after the GW-U device preprocesses, according to afirst forwarding rule, a first multicast group removal request messagesent by the base station. The GW-C device further includes a multicastmanagement unit configured to remove, according to the preprocessedfirst multicast group removal request message, the base station from theIP multicast group using the GW-U device as the source point.

With reference to any possible implementation of the fourth aspect, orthe first to the tenth possible implementations of the fourth aspect, inan eleventh possible implementation, if the sending manner on the SGi-mbinterface between the broadcast/multicast service center and the gatewayuser plane device is the multicast manner, the third interaction unit isfurther configured to send a multicast group removal instruction messageto the GW-U device. The multicast group removal instruction messageincludes a second multicast group removal request message and is forinstructing the GW-U device to send the second multicast group removalrequest message to the broadcast/multicast service center. The secondmulticast group removal request message is for instructing thebroadcast/multicast service center to remove the GW-U device from an IPmulticast group using the broadcast/multicast service center as a sourcepoint.

According to a fifth aspect, another GW-C device includes a processor, acommunications interface, a memory, and a communications bus. Theprocessor, the communications interface, and the memory communicate witheach other using the communications bus. The memory is configured tostore program code. The processor invokes the program code stored in thememory to implement operations that include performing core networksignaling interaction with a broadcast/multicast service center and amobility management entity. The operations further include sending aforwarding indication message to a gateway user plane GW-U device. Theforwarding indication message is for instructing the GW-U device toprocess a packet received by the GW-U device. The operations furtherinclude receiving and processing signaling sent by the GW-U deviceaccording to the forwarding indication message. The signaling is sent bythe base station to the GW-U device.

In a first possible implementation of the fifth aspect, the operationsfurther include, in a session establishment procedure, receiving a firstsession start request message sent by the broadcast/multicast servicecenter and sending a second session start request message to themobility management entity. The first session start request message isfor establishing a bearer between the GW-U device and thebroadcast/multicast service center, and the second session start requestmessage is for establishing a bearer between the base station and theGW-U device.

With reference to the fifth aspect or the first possible implementationof the fifth aspect, in a second possible implementation, the GW-Udevice connects to the broadcast/multicast service center using anSGi-mb interface, and the operations further include allocating, when asending manner on the SGi-mb interface is a unicast manner, adestination UDP port corresponding to the SGi-mb interface.

With reference to any possible implementation of the fifth aspect, orthe first to the second possible implementations of the fifth aspect, ina third possible implementation, the GW-U device connects to thebroadcast/multicast service center using an SGi-mb interface, and theoperations further include sending, when a sending manner on the SGi-mbinterface is a multicast manner, a multicast group join instructionmessage to the GW-U device. The multicast group join instruction messageincludes a first multicast group join request message and is forinstructing the GW-U device to send the first multicast group joinrequest message to the broadcast/multicast service center.

With reference to any possible implementation of the fifth aspect, orthe first to the third possible implementations of the fifth aspect, ina fourth possible implementation, the GW-U device connects to the basestation using an M1 interface, and the operations further includeallocating an IP multicast address of the M1 interface and a tunnelidentifier. The IP multicast address is for identifying an IP multicastgroup using the GW-U device as a source point.

With reference to any possible implementation of the fifth aspect, orthe first to the fourth possible implementations of the fifth aspect, ina fifth possible implementation, the forwarding indication messageincludes a first forwarding rule, and the first forwarding rule is usedwhen the GW-U device processes the signaling sent by the base station tothe GW-U device. The operations further include receiving a preprocessedsecond multicast group join request message sent by the GW-U device. Thepreprocessed second multicast group join request message is obtainedafter the GW-U device preprocesses, according to the first forwardingrule, a second multicast group join request message sent by the basestation. The operations further include adding, according to thepreprocessed second multicast group join request message, the basestation into the IP multicast group using the GW-U device as the sourcepoint.

With reference to any possible implementation of the fifth aspect, orthe first to the fifth possible implementations of the fifth aspect, ina sixth possible implementation, the operations further include, in asession termination procedure, receiving a first session terminationrequest message sent by the broadcast/multicast service center, wherethe first session termination request message including specified timeinformation, and releasing a bearer context at a moment specified by thespecified time information.

With reference to any possible implementation of the fifth aspect, orthe first to the sixth possible implementations of the fifth aspect, ina seventh possible implementation, the operations further includesending the forwarding indication message to the GW-U device at themoment specified by the specified time information. The forwardingindication message includes a rule deletion instruction, such that theGW-U device deletes, according to the rule deletion instruction, asecond forwarding rule used when the GW-U device processes abroadcast/multicast service data packet.

With reference to any possible implementation of the fifth aspect, orthe first to the seventh possible implementations of the fifth aspect,in an eighth possible implementation, the operations further includesending a second session termination request message to the mobilitymanagement entity. The second session termination request messageincludes the specified time information, such that the mobilitymanagement entity sends the specified time information to the basestation, and the base station releases the bearer context according tothe specified time information.

With reference to any possible implementation of the fifth aspect, orthe first to the eighth possible implementations of the fifth aspect, ina ninth possible implementation, the operations further includereceiving a preprocessed first multicast group removal request message.The preprocessed first multicast group removal request message isobtained after the GW-U device preprocesses, according to a firstforwarding rule, a first multicast group removal request message sent bythe base station. The operations further include removing, according tothe preprocessed first multicast group removal request message, the basestation from the IP multicast group using the GW-U device as the sourcepoint.

With reference to any possible implementation of the fifth aspect, orthe first to the ninth possible implementations of the fifth aspect, ina tenth possible implementation, if the sending manner on the SGi-mbinterface between the broadcast/multicast service center and the gatewayuser plane device is the multicast manner, the operations furtherinclude sending a multicast group removal instruction message to theGW-U device. The multicast group removal instruction message includes asecond multicast group removal request message and is for instructingthe GW-U device to send the second multicast group removal requestmessage to the broadcast/multicast service center. The second multicastgroup removal request message is for instructing the broadcast/multicastservice center to remove the GW-U device from an IP multicast groupusing the broadcast/multicast service center as a source point.

According to a sixth aspect, an eMBMS system management method includesreceiving, by a GW-U device, a forwarding indication message sent by aGW-C device, the forwarding indication message for instructing the GW-Udevice to process a packet received by the GW-U device. The methodfurther includes receiving signaling sent by a base station and sendingthe signaling to the GW-C device according to the forwarding indicationmessage. The method further includes, in a data transmission procedure,receiving a broadcast/multicast service data packet sent by abroadcast/multicast service center and sending the broadcast/multicastservice data packet to the base station according to the forwardingindication message.

In a first possible implementation of the sixth aspect, the GW-U deviceconnects to the broadcast/multicast service center using an SGi-mbinterface, and the method further includes, when a sending manner on theSGi-mb interface is a multicast manner, receiving a multicast group joininstruction message sent by the GW-C device to the GW-U device. Themulticast group join instruction message includes a first multicastgroup join request message. The method further include sending the firstmulticast group join request message to the broadcast/multicast servicecenter, such that the broadcast/multicast service center adds, accordingto the first multicast group join request message, the GW-U device intoan IP multicast group using the broadcast/multicast service center as asource point.

With reference to the first aspect or the first possible implementationof the first aspect, in a second possible implementation, the forwardingindication message includes a first forwarding rule, and the firstforwarding rule is used when the GW-U device processes the signalingsent by the base station to the GW-U device. Receiving signaling sent bya base station and sending the signaling to the GW-C device according tothe forwarding indication message includes receiving a second multicastgroup join request message sent by the base station, preprocessing thesecond multicast group join request message according to the firstforwarding rule, and sending a preprocessed second multicast group joinrequest message to the GW-C device, such that the GW-C device adds,according to the preprocessed second multicast group join requestmessage, the base station into an IP multicast group using the GW-Udevice as a source point.

With reference to any possible implementation of the sixth aspect, orthe first to the second possible implementations of the sixth aspect, ina third possible implementation, the forwarding indication messageincludes a second forwarding rule, and the second forwarding rule isused when the GW-U device processes the packet sent by thebroadcast/multicast service center to the GW-U device. Sending thebroadcast/multicast service data packet to the base station according tothe forwarding indication message includes sending thebroadcast/multicast service data packet to the base station according tothe second forwarding rule.

With reference to any possible implementation of the sixth aspect, orthe first to the third possible implementations of the sixth aspect, ina fourth possible implementation, the forwarding indication messageincludes a rule deletion instruction, and the method further includesdeleting, according to the rule deletion instruction, a secondforwarding rule used when the GW-U device processes thebroadcast/multicast service data packet.

With reference to any possible implementation of the sixth aspect, orthe first to the fourth possible implementations of the sixth aspect, ina fifth possible implementation, receiving signaling sent by a basestation, and sending the signaling to the GW-C device according to theforwarding indication message includes receiving a first multicast groupremoval request message sent by the base station, preprocessing thefirst multicast group removal request message according to a firstforwarding rule, and sending a preprocessed first multicast groupremoval request message to the GW-C device, such that the GW-C deviceremoves, according to the preprocessed first multicast group removalrequest message, the base station from an IP multicast group using theGW-U device as a source point.

With reference to any possible implementation of the sixth aspect, orthe first to the fifth possible implementations of the sixth aspect, ina sixth possible implementation, if the sending manner on the SGi-mbinterface between the broadcast/multicast service center and the gatewayuser plane device is the multicast manner, the method further includesreceiving a multicast group removal instruction message sent by the GW-Cdevice to the GW-U device, the multicast group removal instructionmessage including a second multicast group removal request message, andsending the second multicast group removal request message to thebroadcast/multicast service center. The second multicast group removalrequest message is for instructing the broadcast/multicast servicecenter to remove the GW-U device from the IP multicast group using thebroadcast/multicast service center as the source point.

According to a seventh aspect, a GW-U device includes a first interationunit, a second interaction unit, and a third interaction unit. The firstinteraction unit is configured to receive a forwarding indicationmessage sent by a GW-C device, the forwarding indication message forinstructing the GW-U device to process a packet received by the GW-Udevice. The second interaction unit is configured to receive signalingsent by a base station. The first interaction unit is further configuredto send the signaling to the GW-C device according to the forwardingindication message. The third interaction unit is configured to receive,in a data transmission procedure, a broadcast/multicast service datapacket sent by a broadcast/multicast service center. The secondinteraction unit is further configured to send the broadcast/multicastservice data packet to the base station according to the forwardingindication message.

In a first possible implementation of the seventh aspect, the GW-Udevice connects to the broadcast/multicast service center using anSGi-mb interface, and the first interaction unit is further configuredto receive, when a sending manner on the SGi-mb interface is a multicastmanner, a multicast group join instruction message sent by the GW-Cdevice to the GW-U device. The multicast group join instruction messageincludes a first multicast group join request message. The thirdinteraction unit is further configured to send the first multicast groupjoin request message to the broadcast/multicast service center, suchthat the broadcast/multicast service center adds, according to the firstmulticast group join request message, the GW-U device into an IPmulticast group using the broadcast/multicast service center as a sourcepoint.

With reference to the seventh aspect or the first possibleimplementation of the seventh aspect, in a second possibleimplementation, the forwarding indication message includes a firstforwarding rule, and the first forwarding rule is used when the GW-Udevice processes the signaling sent by the base station to the GW-Udevice. The second interaction unit is configured to receive a secondmulticast group join request message sent by the base station The firstinteraction unit is configured to preprocess the second multicast groupjoin request message according to the first forwarding rule and send apreprocessed second multicast group join request message to the GW-Cdevice, such that the GW-C device adds, according to the preprocessedsecond multicast group join request message, the base station into an IPmulticast group using the GW-U device as a source point.

With reference to any possible implementation of the seventh aspect, orthe first to the second possible implementations of the seventh aspect,in a third possible implementation, the forwarding indication messageincludes a second forwarding rule, and the second forwarding rule isused when the GW-U device processes the packet sent by thebroadcast/multicast service center to the GW-U device. The secondinteraction unit is configured to send the broadcast/multicast servicedata packet to the base station according to the second forwarding rule.

With reference to any possible implementation of the seventh aspect, orthe first to the third possible implementations of the seventh aspect,in a fourth possible implementation, the forwarding indication messageincludes a rule deletion instruction and the GW-U device furtherincludes a rule deletion unit that is configured to delete, according tothe rule deletion instruction, a second forwarding rule used when theGW-U device processes the broadcast/multicast service data packet.

With reference to any possible implementation of the seventh aspect, orthe first to the fourth possible implementations of the seventh aspect,in a fifth possible implementation, the second interaction unit isfurther configured to receive a first multicast group removal requestmessage sent by the base station. The first interaction unit is furtherconfigured to preprocess the first multicast group removal requestmessage according to a first forwarding rule and send a preprocessedfirst multicast group removal request message to the GW-C device, suchthat the GW-C device removes, according to the preprocessed firstmulticast group removal request message, the base station from an IPmulticast group using the GW-U device as a source point.

With reference to any possible implementation of the seventh aspect, orthe first to the fifth possible implementations of the seventh aspect,in a sixth possible implementation, if the sending manner on the SGi-mbinterface between the broadcast/multicast service center and the gatewayuser plane device is the multicast manner, the first interaction unit isfurther configured to receive a multicast group removal instructionmessage sent by the GW-C device to the GW-U device. The multicast groupremoval instruction message includes a second multicast group removalrequest message. The third interaction unit is further configured tosend the second multicast group removal request message to thebroadcast/multicast service center. The second multicast group removalrequest message is for instructing the broadcast/multicast servicecenter to remove the GW-U device from the IP multicast group using thebroadcast/multicast service center as the source point.

According to an eighth aspect, another GW-U device includes a processor,a communications interface, a memory, and a communications bus. Theprocessor, the communications interface, and the memory communicate witheach other using the communications bus. The memory is configured tostore program code. The processor invokes the program code stored in thememory, to implement operations that include receiving a forwardingindication message sent by a GW-C device, the forwarding indicationmessage for instructing the GW-U device to process a packet received bythe GW-U device. The operations further include receiving signaling sentby a base station and sending the signaling to the GW-C device accordingto the forwarding indication message. The operations further include, ina data transmission procedure, receiving a broadcast/multicast servicedata packet sent by a broadcast/multicast service center and sending thebroadcast/multicast service data packet to the base station according tothe forwarding indication message.

In a first possible implementation of the eighth aspect, the GW-U deviceconnects to the broadcast/multicast service center using an SGi-mbinterface, and operations further include, when a sending manner on theSGi-mb interface is a multicast manner, receiving a multicast group joininstruction message sent by the GW-C device to the GW-U device, themulticast group join instruction message including a first multicastgroup join request message, and sending the first multicast group joinrequest message to the broadcast/multicast service center, such that thebroadcast/multicast service center adds, according to the firstmulticast group join request message, the GW-U device into an IPmulticast group using the broadcast/multicast service center as a sourcepoint.

With reference to the eighth aspect or the first possible implementationof the eighth aspect, in a second possible implementation, theforwarding indication message includes a first forwarding rule that isused when the GW-U device processes the signaling sent by the basestation to the GW-U device. The operations further include receiving asecond multicast group join request message sent by the base station,preprocessing the second multicast group join request message accordingto the first forwarding rule, and sending a preprocessed secondmulticast group join request message to the GW-C device, such that theGW-C device adds, according to the preprocessed second multicast groupjoin request message, the base station into an IP multicast group usingthe GW-U device as a source point.

With reference to any possible implementation of the eighth aspect, orthe first to the second possible implementations of the eighth aspect,in a third possible implementation, the forwarding indication messageincludes a second forwarding rule that is used when the GW-U deviceprocesses the packet sent by the broadcast/multicast service center tothe GW-U device and the operations further include sending thebroadcast/multicast service data packet to the base station according tothe second forwarding rule.

With reference to any possible implementation of the eighth aspect, orthe first to the third possible implementations of the eighth aspect, ina fourth possible implementation, the forwarding indication messageincludes a rule deletion instruction and the operations further includedeleting, according to the rule deletion instruction, a secondforwarding rule used when the GW-U device processes thebroadcast/multicast service data packet.

With reference to any possible implementation of the eighth aspect, orthe first to the fourth possible implementations of the eighth aspect,in a fifth possible implementation, the operations further includereceiving a first multicast group removal request message sent by thebase station, preprocessing the first multicast group removal requestmessage according to a first forwarding rule, and sending a preprocessedfirst multicast group removal request message to the GW-C device, suchthat the GW-C device removes, according to the preprocessed firstmulticast group removal request message, the base station from an IPmulticast group using the GW-U device as a source point.

With reference to any possible implementation of the eighth aspect, orthe first to the fifth possible implementations of the eighth aspect, ina sixth possible implementation, if the sending manner on the SGi-mbinterface between the broadcast/multicast service center and the gatewayuser plane device is the multicast manner, the operations furtherinclude receiving a multicast group removal instruction message sent bythe GW-C device to the GW-U device, the multicast group removalinstruction message including a second multicast group removal requestmessage, and sending the second multicast group removal request messageto the broadcast/multicast service center. The second multicast groupremoval request message is for instructing the broadcast/multicastservice center to remove the GW-U device from the IP multicast groupusing the broadcast/multicast service center as the source point.

According to certain examples of the foregoing embodiments, the eMBMSsystem includes the broadcast/multicast service center, the basestation, the mobility management entity connected to the base station,the GW-C device connected to the mobility management entity and thebroadcast/multicast service center, and the GW-U device connected to thebase station and the broadcast/multicast service center. The GW-C deviceis configured to perform core network signaling interaction with thebroadcast/multicast service center and the mobility management entity,and to send the forwarding indication message to the GW-U device. Theforwarding indication message is for instructing the GW-U device toprocess the packet received by the GW-U device. The GW-U device isconfigured to receive the signaling sent by the base station, and tosend the signaling to the GW-C device according to the forwardingindication message. The GW-C device is further configured to receive andprocess the signaling sent by the GW-U device. The GW-U device isfurther configured to, in the data transmission procedure, receive thebroadcast/multicast service data packet sent by the broadcast/multicastservice center and send the broadcast/multicast service data packet tothe base station according to the forwarding indication message.

In this way, the GW-U device and the GW-C device may be two separatedevices, the GW-C device being responsible for processing allsession-related signaling, and the GW-U device being responsible forreceiving and forwarding, in the data transmission procedure, thebroadcast/multicast service data packet sent by the broadcast/multicastservice center. Therefore, in certain embodiments, after a new functionis added into or a new service is deployed in the GW-C device, the GW-Udevice does not need to be modified, allowing the GW-C device and theGW-U device to independently evolve.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions in embodiments of the presentdisclosure more clearly, the following briefly describes theaccompanying drawings used for describing the embodiments. Theaccompanying drawings in the following description show merely someembodiments of the present disclosure.

FIG. 1 is a schematic structural diagram of an existing eMBMS systemaccording to the present disclosure;

FIG. 2 is a schematic structural diagram of an eMBMS system according toan embodiment of the present disclosure;

FIG. 3 is a schematic structural diagram of another eMBMS systemaccording to an embodiment of the present disclosure;

FIG. 4 is a schematic flowchart of an eMBMS system management methodaccording to an embodiment of the present disclosure;

FIG. 5A and FIG. 5B are a schematic diagram of a session establishmentprocedure of an eMBMS system according to an embodiment of the presentdisclosure;

FIG. 6A and FIG. 6B are a schematic diagram of a session terminationprocedure of an eMBMS system according to an embodiment of the presentdisclosure;

FIG. 7 is a schematic flowchart of another eMBMS system managementmethod according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of a gateway control planedevice according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of another gateway controlplane device according to an embodiment of the present disclosure;

FIG. 10 is a schematic flowchart of still another eMBMS systemmanagement method according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a gateway user plane deviceaccording to an embodiment of the present disclosure; and

FIG. 12 is a schematic structural diagram of another gateway user planedevice according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

To make the objectives, technical solutions, and advantages ofembodiments of the present disclosure clearer, the following describesthe technical solutions in embodiments of the present disclosure withreference to the accompanying drawings. The described embodiments aresome but not all of the embodiments of the present disclosure.

To help a person skilled in the art understand the solutions, technicalterms used in the present disclosure are first described:

A Multimedia Broadcast and Multicast Service (MBMS) is a mobile devicemultimedia technical solution that is based on a mobile communicationssystem and that is proposed by the 3^(rd) Generation Partnership Project(3GPP). An eMBMS system provided by Long Term Evolution (LTE) supportsan evolved multimedia broadcast/multicast service, and the evolvedmultimedia broadcast/multicast service can provide streaming media ofhigher quality and a timely broadcast service.

A network architecture diagram of the eMBMS system is shown in FIG. 1.It should be noted that a multi-cell/multicast coordination entity inthe eMBMS system is a logical entity, and may independently exist in theeMBMS system, or may be integrated into another entity network elementsuch as a base station. The multi-cell/multicast coordination entity ismainly configured to allocate radio resources used by all base stationsin a same multimedia broadcast multicast service single frequencynetwork (MBSFN) area.

A mobility management entity in the eMBMS system is configured toprovide a control plane function used when an evolved universalterrestrial radio access network (E-UTRAN) accesses a core network. TheE-UTRAN may include the base station and the multi-cell/multicastcoordination entity. Interaction between the mobility management entityand the base station that is described below may be considered asinteraction between the mobility management entity and the E-UTRAN.

Software-defined networking (SDN) is a network architecture, candecouple a control function from a forwarding function, and hascharacteristics of centralized control and open programming interface.

The OpenFlow protocol is an interface protocol between a gateway controlplane device and a gateway user plane device in an SDN architecture, andis intended to resolve various bottlenecks generated when a currentnetwork faces a new service.

Embodiment 1

This embodiment of the present disclosure provides an eMBMS system 20.As shown in FIG. 2, the eMBMS system 20 includes a broadcast/multicastservice center 201, a base station 202, a mobility management entity 203connected to base station 202, a gateway control plane (GW-C) device 204connected to mobility management entity 203 and broadcast/multicastservice center 201, and a gateway user plane (GW-U) device 205 connectedto base station 202 and broadcast/multicast service center 201. GW-Cdevice 204 connects to GW-U device 205.

GW-C device 204 is configured to perform core network signalinginteraction with broadcast/multicast service center 201 and mobilitymanagement entity 203.

GW-C device 204 is further configured to send a forwarding indicationmessage to GW-U device 205. The forwarding indication message is used toinstruct GW-U device 205 to process a packet received by GW-U device205.

GW-U device 205 is configured to receive signaling sent by base station202 and send the signaling to GW-C device 204 according to theforwarding indication message.

GW-C device 204 is further configured to receive and process thesignaling sent by GW-U device 205.

GW-U device 205 is further configured to, in a data transmissionprocedure, receive a broadcast/multicast service data packet sent bybroadcast/multicast service center 201, and send the broadcast/multicastservice data packet to base station 202 according to the forwardingindication message.

It should be noted that mobility management entity 203, GW-C device 204,GW-U device 205, and broadcast/multicast service center 201 arefunctional entities in a core network, and base station 202 is afunctional entity in an access network. In this way, core networksignaling includes signaling exchanged between functional entities inthe core network. The signaling sent by base station 202 to GW-U device205 includes a message for requesting to join an IP multicast group anda message for requesting to exit an IP multicast group.

In addition, although a multi-cell/multicast coordination entity is notshown in FIG. 2, a person skilled in the art would understand that themulti-cell/multicast coordination entity may be disposed in a physicalentity together with base station 202, or may be individually disposed.For details, refer to the description of the technical terms at thebeginning of the specification.

In this way, GW-U device 205 and GW-C device 204 may be two separatedevices, the GW-C device being responsible for processing allsession-related signaling, and the GW-U device being responsible forreceiving and forwarding, in the data transmission procedure, thebroadcast/multicast service data packet sent by the broadcast/multicastservice center. Therefore, after a new function is added into or a newservice is deployed in GW-C device 204, GW-U device 205 does not need tobe modified, allowing GW-C device 204 and GW-U device 205 toindependently evolve.

To assist a person skilled in the art in understanding the eMBMS systemprovided in embodiments of the present disclosure more easily, thefollowing describes the functional entities in the eMBMS system ingreater detail.

First, as shown in FIG. 1, in an existing eMBMS system, an SGmbinterface is an interface between a broadcast/multicast service centerand an MBMS gateway control plane, and is responsible for transitingsignaling between the broadcast/multicast service center and the MBMSgateway control plane. An SGi-mb interface is an interface between thebroadcast/multicast service center and an MBMS gateway user plane, andis responsible for receiving a broadcast/multicast service data packetfrom the broadcast/multicast service center.

Therefore, a specific connecting structure of the eMBMS system 20provided in this embodiment of the present disclosure is shown in FIG.3. FIG. 3 shows an individually-disposed multi-cell/multicastcoordination entity 206. GW-C device 204 connects to broadcast/multicastservice center 201 using an SGmb interface, GW-U device 205 connects tobroadcast/multicast service center 201 using an SGi-mb interface, GW-Cdevice 204 connects to mobility management entity 203 using an Sminterface, GW-U device 205 connects to base station 202 using an M1interface, and CW-C device 204 connects to gateway user plane device 205using an OpenFlow interface. It may be learned from the description ofthe technical terms at the beginning of the specification that GW-Cdevice 204 in the present disclosure may control behavior of GW-U device205 using the OpenFlow protocol.

Next, it should be noted that a service procedure of the eMBMS systemincludes a session establishment procedure, a data transmissionprocedure, and a session termination procedure. The following describesoperations of the functional entities in the foregoing three proceduresin detail.

Optionally, in the session establishment procedure, GW-C device 204 isconfigured to receive a first session start request message sent by thebroadcast/multicast service center and send a second session startrequest message to mobility management entity 203. The first sessionstart request message is used to establish a bearer between GW-U device205 and broadcast/multicast service center 201, and the second sessionstart request message is used to establish a bearer between base station202 and GW-U device 205.

It should be noted that bearer establishment includes two functionalentities creating a bearer context of an MBMS service and storing asession attribute. In this way, before sending the first session startrequest message, broadcast/multicast service center 201 may establish abearer context of an MBMS service and send the first session startrequest message that includes session-related information to GW-C device204. After receiving the first session start request message, GW-Cdevice 204 establishes the bearer context of the MBMS service accordingto the first session start request message to complete establishment ofthe bearer between GW-U device 205 and broadcast/multicast servicecenter 201.

Further, GW-C device 204 sends the second session start request messagethat includes session-related information to mobility management entity203, so that mobility management entity 203 sends the session-relatedinformation to base station 202. Base station 202 establishes the bearercontext of the MBMS service to complete establishment of the bearerbetween base station 202 and GW-U device 205. The bearer betweenbroadcast/multicast service center 201 and GW-U device 205 and thebearer between GW-U device 205 and base station 202 are used to transmitthe broadcast/multicast service data packet.

Optionally, in the session establishment procedure, GW-C device 204 isfurther configured to allocate, when a sending manner on the SGi-mbinterface is a unicast manner, a destination User Datagram Protocol(UDP) port corresponding to the SGi-mb interface.

For example, the first session start request message may further includeidentification information used to identify the sending manner on theSGi-mb interface. In this way, after receiving the first session startrequest message, GW-C device 204 may determine the sending manner on theSGi-mb interface according to the identification information. It shouldbe noted that broadcast/multicast service center 201 may send thebroadcast/multicast service data packet to GW-U device 205 in a unicastmanner or a multicast manner. If the sending manner on the SGi-mbinterface is the unicast manner, GW-C device 204 may allocate thedestination UDP port corresponding to the SGi-mb interface, so that GW-Udevice 205 receives, using the UDP port, the broadcast/multicast servicedata packet sent by broadcast/multicast service center 201.

Optionally, GW-C device 204 is further configured to send, when asending manner on the SGi-mb interface is a multicast manner, amulticast group join instruction message to GW-U device 205. Themulticast group join instruction message includes a first multicastgroup join request message and is used to instruct GW-U device 205 tosend the first multicast group join request message tobroadcast/multicast service center 201. GW-U device 205 is furtherconfigured to send the first multicast group join request message tobroadcast/multicast service center 201. Broadcast/multicast servicecenter 201 is configured to add, according to the first multicast groupjoin request message, GW-U device 205 into an IP multicast group usingbroadcast/multicast service center 201 as a source point, such thatbroadcast/multicast service center 201 can send the broadcast/multicastservice data packet to GW-U device 205 in a multicast manner.

For example, the OpenFlow protocol is used as an interface protocolbetween GW-U device 205 and GW-C device 204. GW-C device 204encapsulates the first multicast group join request message using theOpenFlow protocol to obtain a packet-out message, that is, the multicastgroup join instruction message. In this way, after receiving themulticast group join instruction message, GW-U device 205 obtains thefirst multicast group join request message by means of parsing, andsends the first multicast group join request message tobroadcast/multicast service center 201 according to an instruction.

Optionally, GW-C device 204 is further configured to allocate an IPmulticast address of the M1 interface and a tunnel identifier. The IPmulticast address is used to identify an IP multicast group using GW-Udevice 205 as a source point.

It should be noted that, after receiving the broadcast/multicast servicedata packet, GW-U device 205 sends the broadcast/multicast service datapacket to all base stations 202 in the IP multicast group using GW-Udevice 205 as the source point. The IP multicast group is marked in amanner of an IP multicast address+a multicast source address, that is,the IP multicast address allocated by GW-C device 204 to the M1interface is used to mark the IP multicast group.

In addition, it should be noted that an interaction packet between GW-Udevice 205 and base station 202 may be encapsulated using the GPRSTunneling Protocol (GTP). The tunnel identifier is a field in the GTPand used to identify a tunnel endpoint.

Optionally, in the session establishment procedure, the forwardingindication message sent by GW-C device 204 to GW-U device 205 includes afirst forwarding rule. The first forwarding rule is a rule used whenGW-U device 205 processes the signaling sent by base station 202 to GW-Udevice 205. In the session establishment procedure, the signaling sentby base station 202 to GW-U device 205 includes a second multicast groupjoin request message. GW-U device 205 is configured to receive thesecond multicast group join request message sent by base station 202,preprocess the second multicast group join request message according tothe first forwarding rule, and send a preprocessed second multicastgroup join request message to GW-C device 204. GW-C device 204 isfurther configured to add, after receiving the preprocessed secondmulticast group join request message and according to the preprocessedsecond multicast group join request message, base station 202 into theIP multicast group using GW-U device 205 as the source point.

As an example, after receiving the first session start request message,GW-C device 204 may send the first forwarding rule to GW-U device 205.The first forwarding rule may indicate a message that needs to beforwarded by GW-U device 205, and preprocessing that needs to beperformed by GW-U device 205 on the message.

For example, the message that is indicated by the first forwarding ruleand is to be forwarded by GW-U device 205 includes the second multicastgroup join request message that is sent by base station 202 and used torequest to join the IP multicast group, and indicates that preprocessingto be performed by GW-U device 205 on the second multicast group joinrequest message is encapsulating the second multicast group join requestmessage using the OpenFlow protocol to obtain a Packet-in message. Thepacket-in message includes a port through which GW-U device 205 receivesthe second multicast group join request message, and the packet-inmessage is the preprocessed second multicast group join request message.

Optionally, in the session establishment procedure, the forwardingindication message sent by GW-C device 204 to GW-U device 205 mayfurther include a second forwarding rule, and the second forwarding ruleis a rule used when GW-U device 205 processes the packet sent bybroadcast/multicast service center 201 to GW-U device 205. GW-U device205 is configured to send the broadcast/multicast service data packet tobase station 202 according to the second forwarding rule after receivingthe broadcast/multicast service data packet.

For example, the second forwarding rule includes a manner that isindicated by GW-C device 204 and in which GW-U device 205 processes thebroadcast/multicast service data packet, and at least one port throughwhich the broadcast/multicast service data packet is output. The atleast one port corresponds to at least one base station 202 in the IPmulticast group using GW-U device 205 as the source point. In this way,after receiving the broadcast/multicast service data packet, GW-U device205 processes the broadcast/multicast service data packet according tothe processing manner of the second forwarding rule and forwards aprocessed broadcast/multicast service data packet to the correspondingat least one base station 202 using the at least one port.

It may be learned from the foregoing description that, in the eMBMSsystem provided in this embodiment of the present disclosure, in thesession establishment procedure, related signaling is processed by GW-Cdevice 204, and GW-U device 205 just forwards the related signaling andthe broadcast/multicast service data packet according to an instructionof GW-C device 204.

Further, in the session termination procedure, GW-C device 204 isfurther configured to receive a first session termination requestmessage sent by broadcast/multicast service center 201. The firstsession termination request message includes specified time information.GW-C device 204 releases a bearer context at a moment specified by thespecified time information.

Further, in the session termination procedure, the forwarding indicationmessage sent by GW-C device 204 to GW-U device 205 includes a ruledeletion instruction. For example, GW-C device 204 sends the forwardingindication message to GW-U device 205 at the moment specified by thespecified time information. GW-U device 205 is further configured todelete, according to the rule deletion instruction, a second forwardingrule used when GW-U device 205 processes the broadcast/multicast servicedata packet.

Optionally, GW-C device 204 is further configured to send a secondsession termination request message to mobility management entity 203.The second session termination request message includes the specifiedtime information, so that mobility management entity 203 sends thespecified time information to base station 202, and base station 202releases the bearer context according to the specified time information.

For example, the first session termination request message includes aservice termination moment. After receiving the first sessiontermination message, GW-C device 204 sends a second session terminationmessage that includes a session termination moment to mobilitymanagement entity 203. After receiving the second session terminationmessage, mobility management entity 203 sends a third sessiontermination message that includes the session termination moment to basestation 202. In this way, when the session termination moment arrives,GW-C device 204, mobility management entity 203, and base station 202may release the bearer context at the same time.

Optionally, in the session termination procedure, GW-U device 205 isfurther configured to receive a first multicast group removal requestmessage sent by base station 202, preprocess the first multicast groupremoval request message according to a first forwarding rule, and send apreprocessed first multicast group removal request message to GW-Cdevice 204. GW-C device 204 is further configured to remove, afterreceiving the preprocessed first multicast group removal requestmessage, and according to the preprocessed first multicast group removalrequest message, base station 202 from the IP multicast group using GW-Udevice 205 as the source point.

Optionally, if the sending manner on the SGi-mb interface betweenbroadcast/multicast service center 201 and GW-U device 205 is themulticast manner, in the session termination procedure, GW-C device 204is further configured to send a multicast group removal instructionmessage to GW-U device 205. The multicast group removal instructionmessage includes a second multicast group removal request message and isused to instruct GW-U device 205 to send the second multicast groupremoval request message to broadcast/multicast service center 201.

GW-U device 205 is further configured to send the second multicast groupremoval request message to broadcast/multicast service center 201. Thesecond multicast group removal request message is used to instructbroadcast/multicast service center 201 to remove GW-U device 205 fromthe IP multicast group using broadcast/multicast service center 201 asthe source point.

For example, the multicast group removal instruction message sent byGW-C device 204 to GW-U device 205 is a Packet-out message encapsulatedusing the OpenFlow protocol. The packet-out message may include thesecond multicast group removal request message and a message forwardingindication. In this way, after receiving the multicast group removalinstruction message, GW-U device 205 sends the second multicast groupremoval request message to broadcast/multicast service center 201according to the message forwarding indication.

It may be learned from the foregoing description that, at the specifiedmoment, the eMBMS system releases a bearer context of a related device,deletes the second forwarding rule used when GW-U device 205 processesthe broadcast/multicast service data packet, and removes base station202 and GW-U device 205 from corresponding IP multicast groups, so as toterminate a broadcast/multicast service. In addition, in this process,related signaling is processed by GW-U device 205, and GW-C device 204just forwards the related signaling according to an instruction of theGW-C.

It should be noted that the foregoing describes the network architectureof the eMBMS system provided in this embodiment of the presentdisclosure, and the operations of GW-C device 204 and GW-U device 205 inthe eMBMS system. The operations of GW-C device 204 and GW-U device 205are not limited by a description sequence, that is, a sequence of theactions executed by GW-C device 204 and the actions executed by GW-Udevice 205 is not limited in the present disclosure. For a specificservice procedure of the eMBMS system provided in this embodiment of thepresent disclosure, refer to an eMBMS system management method providedin a next embodiment in the specification.

According to the foregoing solutions, the eMBMS system includesbroadcast/multicast service center 201, base station 202, mobilitymanagement entity 203 connected to base station 202, GW-C device 204connected to mobility management entity 203 and broadcast/multicastservice center 201, and GW-U device 205 connected to base station 202and broadcast/multicast service center 201. GW-C device 204 isconfigured to: perform core network signaling interaction withbroadcast/multicast service center 201 and mobility management entity203, and send the forwarding indication message to GW-U device 205. Theforwarding indication message is used to instruct GW-U device 205 toprocess the packet received by GW-U device 205. GW-U device 205 isconfigured to receive the signaling sent by base station 202, and sendthe signaling to GW-C device 204 according to the forwarding indicationmessage. GW-C device 204 is further configured to receive and processthe signaling sent by GW-U device 205. GW-U device 205 is furtherconfigured to, in the data transmission procedure, receive thebroadcast/multicast service data packet sent by broadcast/multicastservice center 201 and send the broadcast/multicast service data packetto base station 202 according to the forwarding indication message.

In this way, GW-U device 205 and GW-C device 204 may be two separatedevices, GW-C device 204 is responsible for processing session-relatedsignaling, and GW-U device 205 is responsible for receiving andforwarding, in the data transmission procedure, the broadcast/multicastservice data packet sent by broadcast/multicast service center 201.Therefore, after a new function is added into or a new service isdeployed in GW-C device 204, GW-U device 205 does not need to bemodified, allowing GW-C device 204 and GW-U device 205 to independentlyevolve.

Embodiment 2

This embodiment of the present disclosure provides an eMBMS systemmanagement method. An eMBMS system includes a broadcast/multicastservice center, a base station, a mobility management entity connectedto the base station, a GW-C device connected to the mobility managemententity and the broadcast/multicast service center, and a GW-U deviceconnected to the base station and the broadcast/multicast servicecenter. The GW-C device connects to the GW-U device.

As shown in FIG. 4, the method includes the following steps:

S401. The GW-C device performs core network signaling interaction withthe broadcast/multicast service center and the mobility managemententity.

S402. The GW-C device sends a forwarding indication message to the GW-Udevice. The forwarding indication message is used to instruct the GW-Udevice to process a packet received by the GW-U device.

S403. The GW-U device receives signaling sent by the base station andsends the signaling to the GW-C device according to the forwardingindication message.

S404. The GW-C device receives and processes the signaling sent by theGW-U device.

S405. In a data transmission procedure, the GW-U device receives abroadcast/multicast service data packet sent by the broadcast/multicastservice center and sends the broadcast/multicast service data packet tothe base station according to the forwarding indication message.

In this way, the GW-U device and the GW-C device may be two separatedevices, the GW-C device being responsible for processing allsession-related signaling, and the GW-U device just being responsiblefor receiving and forwarding, in the data transmission procedure, thebroadcast/multicast service data packet sent by the broadcast/multicastservice center. Therefore, after a new function is added into or a newservice is deployed in the GW-C device, the GW-U device does not need tobe modified, allowing the GW-C device and the GW-U device toindependently evolve.

The following describes the eMBMS system management method provided inthis embodiment of the present disclosure in detail.

First, it should be noted that a service procedure of the eMBMS systemmay include a session establishment procedure, a data transmissionprocedure, and a session termination procedure.

In the session establishment procedure, step S401 includes receiving afirst session start request message sent by the broadcast/multicastservice center and sending, by the GW-C device, a second session startrequest message to the mobility management entity. The first sessionstart request message is used to establish a bearer between the GW-Udevice and the broadcast/multicast service center, and the secondsession start request message is used to establish a bearer between thebase station and the GW-U device.

Optionally, the GW-U device connects to the broadcast/multicast servicecenter using an SGi-mb interface, and the method further includesallocating, when a sending manner on the SGi-mb interface is a unicastmanner, by the GW-C device a destination UDP port corresponding to theSGi-mb interface.

Optionally, the GW-U device connects to the broadcast/multicast servicecenter using an SGi-mb interface, and the method further includes, whena sending manner on the SGi-mb interface is a multicast manner, sendingby the GW-C device a multicast group join instruction message to theGW-U device. The multicast group join instruction message includes afirst multicast group join request message, and is used to instruct theGW-U device to send the first multicast group join request message tothe broadcast/multicast service center. The method further includessending by the GW-U device the first multicast group join requestmessage to the broadcast/multicast service center and adding, by thebroadcast/multicast service center according to the first multicastgroup join request message, the GW-U device into an IP multicast groupusing the broadcast/multicast service center as a source point.

Optionally, the GW-U device connects to the base station using an M1interface, and the method further includes allocating by the GW-C devicean IP multicast address of the M1 interface and a tunnel identifier. TheIP multicast address is used to identify an IP multicast group using theGW-U device as a source point.

Optionally, in the session establishment procedure, the forwardingindication message includes a first forwarding rule, and the firstforwarding rule is a rule used when the GW-U device processes thesignaling sent by the base station to the GW-U device. In addition, inthe session establishment procedure, the signaling sent by the basestation to the GW-U device includes a second multicast group joinrequest message, and step S402 includes receiving by the GW-U device thesecond multicast group join request message sent by the base station,preprocessing the second multicast group join request message accordingto the first forwarding rule, and sending a preprocessed secondmulticast group join request message to the GW-C device.

Step S403 includes adding, after receiving the preprocessed secondmulticast group join request message, by the GW-C device according tothe preprocessed second multicast group join request message, the basestation into the IP multicast group using the GW-U device as the sourcepoint.

Optionally, in the session establishment procedure, the forwardingindication message sent by the GW-C device to the GW-U device mayfurther include a second forwarding rule, and the second forwarding ruleis a rule used when the GW-U device processes the packet sent by thebroadcast/multicast service center to the GW-U device. That is, the GW-Udevice sends the broadcast/multicast service data packet to the basestation according to the second forwarding rule after receiving thebroadcast/multicast service data packet.

To assist a person skilled in the art in understanding the eMBMS systemmanagement method provided in this embodiment of the present disclosure,the following describes a method of session establishment to transmitdata using a specific embodiment. As shown in FIG. 5A and FIG. 5B, themethod procedure includes the following steps:

S501. A broadcast/multicast service center sends a first session startrequest message to a GW-C device.

For example, the broadcast/multicast service center may send the firstsession start request message to the GW-C device after establishing abearer context of an MBMS service.

The first session start request message is used to establish a bearerbetween a GW-U device and the broadcast/multicast service center.

S502. After receiving the first session start request message, the GW-Cdevice establishes a bearer context of an MBMS service.

Optionally, after receiving the first session start request message, thegateway control plane device may further determine a sending manner onan SGi-mb interface. It should be noted that the SGi-mb interface is aninterface between the GW-U device and the broadcast/multicast servicecenter. The broadcast/multicast service center may send abroadcast/multicast service data packet to the GW-U device in a unicastmanner or may send a broadcast/multicast service data packet to the GW-Udevice in a multicast manner.

When determining that the sending manner on the SGi-mb interface is aunicast manner, the GW-C device may allocate a destination UDP portcorresponding to the SGi-mb interface. In this way, the GW-U device mayreceive, using the UDP port, the broadcast/multicast service data packetsent by the broadcast/multicast service center to the GW-U device in aunicast manner.

This embodiment of the present disclosure is described using an examplein which the broadcast/multicast service center uses a multicast manner.

Optionally, after receiving the first session start request message, theGW-C device may further allocate an IP multicast address of an M1interface between the GW-U device and a base station and a tunnelidentifier.

It should be noted that, after receiving the broadcast/multicast servicedata packet, the GW-U device may send the broadcast/multicast servicedata packet to all base stations in an IP multicast group using the GW-Udevice as a source point. The IP multicast group is marked in a mannerof an IP multicast address+a multicast source address, that is, the IPmulticast address allocated by GW-C device to the M1 interface is usedto mark the IP multicast group.

In addition, it should be noted that an interaction packet between theGW-U device and the base station may be encapsulated using the GPRSTunneling Protocol. The tunnel identifier is a field in the GTP and usedto identify a tunnel endpoint.

S503. The GW-C device sends a first session start response message tothe broadcast/multicast service center.

S504. The GW-C device sends a second session start request message to amobility management entity.

S505. The GW-C device sends a first forwarding rule to a GW-U device.

The first forwarding rule may indicate a message that needs to beforwarded by the GW-U device and preprocessing that needs to beperformed by the GW-U device on the message. For details, refer to thefollowing step S513.

S506. After receiving the second session start request message, themobility management entity establishes a bearer context of an MBMSservice.

S507. The mobility management entity sends a third session start requestmessage to a base station.

S508. After receiving the third session start request message, the basestation establishes a bearer context of an MBMS service.

S509. The base station sends a third session start response message tothe mobility management entity.

S510. The mobility management entity sends a second session startresponse message to the GW-C device.

S511. The base station creates a radio resource for MBMS datatransmission.

S512. The base station sends a multicast group join request message tothe GW-U device.

S513. The GW-U device preprocesses the multicast group join requestmessage according to the first forwarding rule.

For example, the preprocessing may be encapsulating the multicast groupjoin request message using the OpenFlow protocol to obtain a Packet-inmessage. The packet-in message includes a port through which the GW-Udevice receives the multicast group join request message, and thepacket-in message is a preprocessed multicast group join requestmessage.

S514. The GW-U device sends a preprocessed multicast group join requestmessage to the GW-C device.

S515. The GW-C device adds, according to the preprocessed multicastgroup join request message, the base station into an IP multicast groupusing the GW-U device as a source point.

S516. The GW-C device sends a multicast group join instruction messageto the GW-U device.

The multicast group join instruction message includes the multicastgroup join request message and is used to instruct the GW-U device tosend the multicast group join request message to the broadcast/multicastservice center.

It should be noted that this embodiment of the present disclosure isdescribed using an example in which the broadcast/multicast servicecenter sends the broadcast/multicast service data packet to the GW-Udevice in a multicast manner. In this case, the GW-U device joins an IPmulticast group using the broadcast/multicast service center as a sourcepoint. Optionally, the broadcast/multicast service center may send thebroadcast/multicast service data packet in a unicast manner.

S517. The GW-U device sends the multicast group join request message inthe multicast group join instruction message to the broadcast/multicastservice center.

S518. The broadcast/multicast service center adds, according to themulticast group join request message, the GW-U device into an IPmulticast group using the broadcast/multicast service center as a sourcepoint.

S519. The GW-C device sends a second forwarding rule to the GW-U device.

S520. The broadcast/multicast service center sends a broadcast/multicastservice data packet to the GW-U device in a multicast manner.

S521. The GW-U device sends the broadcast/multicast service data packetto the base station according to the second forwarding rule.

It should be noted that, for ease of description, the foregoing methodis represented as a combination of a series of actions. However, aperson skilled in the art would understand that the present disclosureis not limited by the described action sequence and that the actionsmentioned are not necessarily required by the present disclosure.

It may be learned from step S501 to step S521 that, in a sessionestablishment procedure and a data transmission procedure,session-related signaling is processed by the GW-C device, and the GW-Udevice is responsible for receiving and forwarding thebroadcast/multicast service data packet in the data transmissionprocedure.

Further, in a session termination procedure, step S401 further includes,in the session termination procedure, receiving by the GW-C device afirst session termination request message sent by thebroadcast/multicast service center, the first session terminationrequest message including specified time information, and releasing bythe GW-C device a bearer context at a moment specified by the specifiedtime information.

Optionally, in the session termination procedure, the forwardingindication message sent by the GW-C device to the GW-U device includes arule deletion instruction. For example, the GW-C device may send therule deletion instruction to the GW-U device at the moment specified bythe specified time information. The GW-U device deletes, according tothe rule deletion instruction, a second forwarding rule used when theGW-U device processes the broadcast/multicast service data packet.

Optionally, step S401 further includes sending by the GW-C device asecond session termination request message to the mobility managemententity, the second session termination request message including thespecified time information, such that the mobility management entitysends the specified time information to the base station and the basestation releases the bearer context according to the specified timeinformation.

Optionally, in the session termination procedure, step S402 furtherincludes receiving by the GW-U device a first multicast group removalrequest message sent by the base station, preprocessing the firstmulticast group removal request message according to a first forwardingrule, and sending a preprocessed first multicast group removal requestmessage to the GW-C device.

Step S403 further includes removing, after receiving the preprocessedfirst multicast group removal request message, by the GW-C deviceaccording to the preprocessed first multicast group removal requestmessage, the base station from the IP multicast group using the GW-Udevice as the source point.

Optionally, if the sending manner on the SGi-mb interface between thebroadcast/multicast service center and the gateway user plane device isthe multicast manner, in the session termination procedure, the methodfurther includes sending by the GW-C device a multicast group removalinstruction message to the GW-U device. The multicast group removalinstruction message includes a second multicast group removal requestmessage and is used to instruct the GW-U device to send the secondmulticast group removal request message to the broadcast/multicastservice center. The method further includes sending by the GW-U devicethe second multicast group removal request message to thebroadcast/multicast service center. The second multicast group removalrequest message is used to instruct the broadcast/multicast servicecenter to remove the GW-U device from the IP multicast group using thebroadcast/multicast service center as the source point.

To assist a person skilled in the art in understanding the eMBMS systemmanagement method provided in the present disclosure, the followingdescribes a session termination procedure using a specific embodiment.As shown in FIG. 6A and FIG. 6B, the session termination procedureincludes the following steps:

S601. A broadcast/multicast service center sends a first sessiontermination request message to a GW-C device.

The first session termination request message includes specified timeinformation.

For example, before sending the first session termination requestmessage, the broadcast/multicast service center may change a usagestatus of a bearer between a GW-U device and the broadcast/multicastservice center into a standby state.

S602. The GW-C device sets and starts a first timer according to thefirst session termination request message.

For example, a time type of a moment specified by the specified timeinformation may be an absolute time type or may be a relative time type.After receiving the first session termination request message, the GW-Cdevice may set and start, according to the specified time information, atimer that expires at the specified moment.

S603. The GW-C device sends a first session termination response messageto the broadcast/multicast service center.

S604. The GW-C device sends a second session termination request messageto a mobility management entity.

The second session termination request message includes the specifiedtime information.

S605. The mobility management entity releases a bearer context of anMBMS service according to the second session termination requestmessage.

S606. The mobility management entity sends a second session terminationresponse message to the GW-C device.

S607. The mobility management entity sends a third session terminationrequest message to a base station.

The third session termination request message includes the specifiedtime information.

S608. The base station sets and starts a second timer according to thethird session termination request message.

For details, refer to the description corresponding to step S602. Thebase station may set and start, according to the specified timeinformation, the second timer that expires at the specified moment.

S609. The base station sends a third session termination responsemessage to the mobility management entity.

S610. When detecting that the second timer expires, the base stationreleases a bearer context of an MBMS service, and releases a radioresource allocated to the MBMS service.

S611. When detecting that the first timer expires, the GW-C devicereleases a bearer context of an MBMS service.

It should be noted that the first timer and the second timer may expireat a same moment, that is, step S610 and step S611 may be performed atthe same time. The present disclosure, however, is not limited to thisscenario.

S612. The GW-C device sends a forwarding indication message to a GW-Udevice.

The forwarding indication message may include a rule deletioninstruction.

For example, after detecting that the first timer expires, the GW-Cdevice sends the forwarding indication message to the GW-U device. Therule deletion instruction included in the forwarding indication messageis used to instruct the GW-U device to delete a second forwarding rule.The second forwarding rule is sent by the GW-C device to the GW-U devicein a service establishment procedure, such that the GW-U deviceprocesses a received broadcast/multicast service data packet accordingto the second forwarding rule.

S613. After receiving the forwarding indication message, the GW-U devicedeletes a second forwarding rule according to a rule deletioninstruction included in the forwarding indication message.

S614. The base station sends a first multicast group removal requestmessage to the GW-U device.

S615. The GW-U device preprocesses the first multicast group removalrequest message according to a first forwarding rule.

The first forwarding rule is sent by the GW-C device to the GW-U devicein the service establishment procedure, such that the GW-U deviceprocesses received signaling according to the first forwarding rule.

For example, the preprocessing may be encapsulating the first multicastgroup removal request message using the OpenFlow protocol to obtain aPacket-in message. The packet-in message includes a port through whichthe GW-U device receives the first multicast group removal requestmessage, and the packet-in message is a preprocessed first multicastgroup removal request message.

S616. The GW-U device sends a preprocessed first multicast group removalrequest message to the GW-C device.

S617. The GW-C device removes, according to the preprocessed firstmulticast group removal request message, the base station from an IPmulticast group using the GW-U device as a source point.

S618. The GW-C device sends a multicast group removal instructionmessage to the GW-U device.

The multicast group removal instruction message includes a secondmulticast group removal request message and is used to instruct the GW-Udevice to send the second multicast group removal request message to thebroadcast/multicast service center.

S619. The GW-U device sends a second multicast group removal requestmessage to the broadcast/multicast service center.

For example, the multicast group removal instruction message sent by theGW-C device to the GW-U device is a Packet-out message encapsulatedusing the OpenFlow protocol. The packet-out message may include thesecond multicast group removal request message and a message forwardingindication. In this way, after receiving the multicast group removalinstruction message, the GW-U device sends the second multicast groupremoval request message to the broadcast/multicast service centeraccording to the message forwarding indication.

S620. The broadcast/multicast service center removes, according to thesecond multicast group removal request message, the GW-U device from anIP multicast group using the broadcast/multicast service center as asource point.

It should be noted that, for ease of description, the foregoing methodis described as a combination of a series of actions. However, a personskilled in the art would understand that the present disclosure is notlimited by the described action sequence and the actions mentioned arenot necessarily required by the present disclosure.

It may be learned from step S601 to step S620 that session-relatedsignaling is processed by the GW-C device in the session terminationprocedure.

According to the eMBMS system management method provided in thisembodiment of the present disclosure, the eMBMS system includes thebroadcast/multicast service center, the base station, the mobilitymanagement entity connected to the base station, the GW-C deviceconnected to the mobility management entity and the broadcast/multicastservice center, and the GW-U device connected to the base station andthe broadcast/multicast service center. The GW-C device is configured toperform core network signaling interaction with the broadcast/multicastservice center and the mobility management entity. The GW-U device isconfigured to receive the signaling sent by the base station and sendthe signaling to the GW-C device according to the first forwarding rule.The GW-C device is further configured to receive and process thesignaling sent by the GW-U device. The GW-U device is further configuredto, in the data transmission procedure, receive the broadcast/multicastservice data packet sent by the broadcast/multicast service center andsend the broadcast/multicast service data packet to the base stationaccording to the second forwarding rule.

In this way, the GW-U device and the GW-C device may be two separatedevices, the GW-C device being responsible for processingsession-related signaling, and the GW-U device being responsible forreceiving and forwarding, in the data transmission procedure, thebroadcast/multicast service data packet sent by the broadcast/multicastservice center. Therefore, after a new function is added into or a newservice is deployed in the GW-C device, the GW-U device does not need tobe modified, allowing the GW-C device and the GW-U device toindependently evolve.

Embodiment 3

This embodiment of the present disclosure provides an eMBMS systemmanagement method, applied to a GW-C device. As shown in FIG. 7, themethod includes the following steps:

S701. The GW-C device performs core network signaling interaction with abroadcast/multicast service center and a mobility management entity.

S702. The GW-C device sends a forwarding indication message to a GW-Udevice. The forwarding indication message is used to instruct the GW-Udevice to process a packet received by the GW-U device.

S703. The GW-C device receives and processes signaling sent by the GW-Udevice according to the forwarding indication message. The signaling issent by the base station to the GW-U device.

For details, refer to Embodiment 1. The mobility management entity, thebroadcast/multicast service center, and the GW-U device in the eMBMSsystem separately connect to the GW-C device. The eMBMS systemmanagement method provided in this embodiment of the present disclosuremainly relates to a method for interacting with the mobility managemententity, the broadcast/multicast service center, and the GW-U device bythe GW-C device, so as to establish a session and terminate a session.The following describes step S701 to step S703 in detail.

Optionally, the GW-C device performing core network signalinginteraction with a broadcast/multicast service center and a mobilitymanagement entity includes, in a session establishment procedure,receiving a first session start request message sent by thebroadcast/multicast service center and sending a second session startrequest message to the mobility management entity. The first sessionstart request message is used to establish a bearer between the GW-Udevice and the broadcast/multicast service center, and the secondsession start request message is used to establish a bearer between thebase station and the GW-U device.

Further, the GW-U device connects to the broadcast/multicast servicecenter using a SGi-mb interface, and the method further includesallocating, when a sending manner on the SGi-mb interface is a unicastmanner, a destination UDP port corresponding to the SGi-mb interface.

For example, the first session start request message may further includeidentification information used to identify the sending manner on theSGi-mb interface. In this way, after receiving the first session startrequest message, the GW-C device may determine the sending manner on theSGi-mb interface according to the identification information. It shouldbe noted that the broadcast/multicast service center may send thebroadcast/multicast service data packet to the GW-U device in a unicastmanner or a multicast manner. If the sending manner on the SGi-mbinterface is the unicast manner, the GW-C device may allocate thedestination UDP port corresponding to the SGi-mb interface, so that theGW-U device receives, using the UDP port, the broadcast/multicastservice data packet sent by the broadcast/multicast service center.

Optionally, the GW-U device connects to the broadcast/multicast servicecenter using an SGi-mb interface, and the method further includes, whena sending manner on the SGi-mb interface is a multicast manner, sendinga multicast group join instruction message to the GW-U device. Themulticast group join instruction message includes a first multicastgroup join request message and is used to instruct the GW-U device tosend the first multicast group join request message to thebroadcast/multicast service center.

For example, the OpenFlow protocol may be used as an interface protocolbetween the GW-U device and the GW-C device. The GW-C deviceencapsulates the first multicast group join request message using theOpenFlow protocol to obtain a Packet-out message, that is, the multicastgroup join instruction message. In this way, after receiving themulticast group join instruction message, the GW-U device obtains thefirst multicast group join request message by means of parsing, andsends the first multicast group join request message to thebroadcast/multicast service center according to an instruction. Thebroadcast/multicast service center adds, according to the firstmulticast group join request message, the GW-U device into an IPmulticast group using the broadcast/multicast service center as a sourcepoint, so that the broadcast/multicast service center can send thebroadcast/multicast service data packet to the GW-U device in amulticast manner.

Optionally, the GW-U device connects to the base station using an M1interface, and the method further includes allocating an IP multicastaddress of the M1 interface and a tunnel identifier, the IP multicastaddress being used to identify an IP multicast group using the GW-Udevice as a source point.

It should be noted that, after receiving the broadcast/multicast servicedata packet, the GW-U device may send the broadcast/multicast servicedata packet to all base stations in the IP multicast group using theGW-U device as the source point. The IP multicast group is marked in amanner of an IP multicast address+a multicast source address, that is,the IP multicast address allocated by GW-C device to the M1 interface isused to mark the IP multicast group.

In addition, it should be noted that an interaction packet between theGW-U device and the base station may be encapsulated using the GPRSTunneling Protocol GTP. The tunnel identifier is a field in the GTP andused to identify a tunnel endpoint.

Optionally, in a specific implementation process, the forwardingindication message sent by the GW-C device to the GW-U device in thesession establishment procedure may include a first forwarding rule, andthe first forwarding rule is a rule used when the GW-U device processesthe signaling sent by the base station to the GW-U device. In this way,step S703 includes receiving, by the GW-C device, a preprocessed secondmulticast group join request message sent by the GW-U device, thepreprocessed second multicast group join request message being obtainedafter the GW-U device preprocesses, according to the first forwardingrule, a second multicast group join request message sent by the basestation. Step S703 further includes adding, according to thepreprocessed second multicast group join request message, the basestation into the IP multicast group using the GW-U device as the sourcepoint.

It may be learned from the foregoing description that, in the eMBMSsystem provided in this embodiment of the present disclosure, in thesession establishment procedure, related signaling is processed by theGW-U device, and the GW-C device just forwards the related signaling andthe broadcast/multicast service data packet according to an instructionof the GW-C.

Further, in a session termination procedure, the gateway control planeGW-C device performing core network signaling interaction with abroadcast/multicast service center includes, in the session terminationprocedure, receiving by the GW-C device a first session terminationrequest message sent by the broadcast/multicast service center, thefirst session termination request message including specified timeinformation, and releasing a bearer context at a moment specified by thespecified time information.

Further, in the session termination procedure, the GW-C device sending aforwarding indication message to a GW-U device includes sending theforwarding indication message to the GW-U device at the moment specifiedby the specified time information. The forwarding indication messageincludes a rule deletion instruction, such that the GW-U device deletes,according to the rule deletion instruction, a second forwarding ruleused when the GW-U device processes a broadcast/multicast service datapacket.

Optionally, in the session termination procedure, the gateway controlplane GW-C device performing core network signaling interaction with amobility management entity includes sending by the GW-C device a secondsession termination request message to the mobility management entity.The second session termination request message includes the specifiedtime information, such that the mobility management entity sends thespecified time information to the base station and the base station canrelease the bearer context according to the specified time information.

For example, the first session termination request message may include aservice termination moment. After receiving the first sessiontermination message, the GW-C device sends a second session terminationmessage that includes a session termination moment to the mobilitymanagement entity. After receiving the second session terminationmessage, the mobility management entity sends a third sessiontermination message that includes the session termination moment to thebase station. In this way, when the session termination moment arrives,the GW-C device, the mobility management entity, and the base stationmay release the bearer context at the same time.

Optionally, in the session termination procedure, the GW-C devicereceiving and processing signaling sent by the GW-U device according tothe forwarding indication message includes receiving, by the GW-Cdevice, a preprocessed first multicast group removal request message.The preprocessed first multicast group removal request message isobtained after the GW-U device preprocesses, according to a firstforwarding rule, a first multicast group removal request message sent bythe base station. The GW-C device receiving and processing signalingsent by the GW-U device according to the forwarding indication messagefurther includes removing, according to the preprocessed first multicastgroup removal request message, the base station from the IP multicastgroup using the GW-U device as the source point.

Optionally, if the sending manner on the SGi-mb interface between thebroadcast/multicast service center and the gateway user plane device isthe multicast manner, the GW-C device may further send a multicast groupremoval instruction message to the GW-U device. The multicast groupremoval instruction message includes a second multicast group removalrequest message and is used to instruct the GW-U device to send thesecond multicast group removal request message to thebroadcast/multicast service center. The second multicast group removalrequest message is used to instruct the broadcast/multicast servicecenter to remove the GW-U device from an IP multicast group using thebroadcast/multicast service center as a source point.

For example, the multicast group removal instruction message sent by theGW-C device to the GW-U device may be a Packet-out message encapsulatedusing the OpenFlow protocol. The packet-out message may include thesecond multicast group removal request message and a message forwardingindication. In this way, after receiving the multicast group removalinstruction message, the GW-U device sends the second multicast groupremoval request message to the broadcast/multicast service centeraccording to the message forwarding indication.

It may be learned from the foregoing description that, at the specifiedmoment, the eMBMS system releases a bearer context of a related device,deletes the second forwarding rule used when the GW-U device processesthe broadcast/multicast service data packet, and removes the basestation and the GW-U device from corresponding IP multicast groups, soas to terminate a broadcast/multicast service. In addition, in thisprocess, related signaling is processed by the GW-U device, and the GW-Cdevice just forwards the related signaling according to an instructionof the GW-C.

In this way, in the session establishment procedure and the sessiontermination procedure, the GW-C device is responsible for processingsession-related signaling and instructing the GW-U device to forwardreceived signaling. Behavior of the GW-U device is controlled by theGW-C device. Therefore, after a new function is added into or a newservice is deployed in the GW-C device, the GW-U device does not need tobe modified, allowing the GW-C device and the GW-U device toindependently evolve.

Embodiment 4

This embodiment of the present disclosure provides a GW-C device 80, soas to implement the eMBMS system management method provided inEmbodiment 3. As shown in FIG. 8, GW-C device 80 includes a firstinteraction unit 81, a second interaction unit 82, and a thirdinteraction unit 83. First interaction unit 81 is configured to performcore network signaling interaction with a broadcast/multicast servicecenter. Second interaction unit 82 is configured to perform core networksignaling interaction with a mobility management entity. Thirdinteraction unit 83 is configured to send a forwarding indicationmessage to a gateway user plane GW-U device. The forwarding indicationmessage is used to instruct the GW-U device to process a packet receivedby the GW-U device. Third interaction unit 83 is further configured toreceive and process signaling sent by the GW-U device according to theforwarding indication message, the signaling being sent by the basestation to the GW-U device.

Optionally, first interaction unit 81 is configured to receive, in asession establishment procedure, a first session start request messagesent by the broadcast/multicast service center. The first session startrequest message is used to establish a bearer between the GW-U deviceand the broadcast/multicast service center.

Second interaction unit 82 is configured to send a second session startrequest message to the mobility management entity. The second sessionstart request message is used to establish a bearer between the basestation and the GW-U device.

Optionally, the GW-U device connects to the broadcast/multicast servicecenter using a SGi-mb interface, and GW-C device 80 further includes anallocation unit 84, configured to allocate, when a sending manner on theSGi-mb interface is a unicast manner, a destination UDP portcorresponding to the SGi-mb interface.

Optionally, the GW-U device connects to the broadcast/multicast servicecenter using a SGi-mb interface, and third interaction unit 83 isfurther configured to send, when a sending manner on the SGi-mbinterface is a multicast manner, a multicast group join instructionmessage to the GW-U device. The multicast group join instruction messageincludes a first multicast group join request message and is used toinstruct the GW-U device to send the first multicast group join requestmessage to the broadcast/multicast service center.

Optionally, the GW-U device connects to the base station using an M1interface, and allocation unit 84 is configured to allocate an IPmulticast address of the M1 interface and a tunnel identifier. The IPmulticast address is used to identify an IP multicast group using theGW-U device as a source point.

Optionally, the forwarding indication message includes a firstforwarding rule, the first forwarding rule is a rule used when the GW-Udevice processes the signaling sent by the base station to the GW-Udevice, and third interaction unit 83 is configured to receive apreprocessed second multicast group join request message sent by theGW-U device. The preprocessed second multicast group join requestmessage is obtained after the GW-U device preprocesses, according to thefirst forwarding rule, a second multicast group join request messagesent by the base station.

GW-C device 80 further includes a multicast management unit 85 that isconfigured to add, according to the preprocessed second multicast groupjoin request message, the base station into the IP multicast group usingthe GW-U device as the source point.

Optionally, first interaction unit 81 is further configured to receive,in a session termination procedure, a first session termination requestmessage sent by the broadcast/multicast service center. The firstsession termination request message includes specified time information.

GW-C device 80 further includes a bearer release unit 86 that isconfigured to release a bearer context at a moment specified by thespecified time information.

Optionally, third interaction unit 83 is configured to send theforwarding indication message to the GW-U device at the moment specifiedby the specified time information. The forwarding indication messageincludes a rule deletion instruction, so that the GW-U device deletes,according to the rule deletion instruction, a second forwarding ruleused when the GW-U device processes a broadcast/multicast service datapacket.

Optionally, second interaction unit 82 is further configured to send asecond session termination request message to the mobility managemententity. The second session termination request message includes thespecified time information, so that the mobility management entity sendsthe specified time information to the base station, and the base stationreleases the bearer context according to the specified time information.

Optionally, third interaction unit 83 is further configured to receive apreprocessed first multicast group removal request message. Thepreprocessed first multicast group removal request message is obtainedafter the GW-U device preprocesses, according to a first forwardingrule, a first multicast group removal request message sent by the basestation.

Multicast management unit 85 is further configured to remove, accordingto the preprocessed first multicast group removal request message, thebase station from the IP multicast group using the GW-U device as thesource point.

Optionally, if the sending manner on the SGi-mb interface between thebroadcast/multicast service center and the gateway user plane device isthe multicast manner, third interaction unit 83 is further configured tosend a multicast group removal instruction message to the GW-U device.The multicast group removal instruction message includes a secondmulticast group removal request message and is used to instruct the GW-Udevice to send the second multicast group removal request message to thebroadcast/multicast service center. The second multicast group removalrequest message is used to instruct the broadcast/multicast servicecenter to remove the GW-U device from an IP multicast group using thebroadcast/multicast service center as a source point.

A person skilled in the art would understand that, for purposes ofconvenience and conciseness, for a specific working process anddescription of the GW-C device, refer to a corresponding process inEmbodiment 3.

According to the GW-C device, in the session establishment procedure andthe session termination procedure, the GW-C device is responsible forprocessing session-related signaling and instructing the GW-U device toforward received signaling. Behavior of the GW-U device is controlled bythe GW-C device. Therefore, after a new function is added into or a newservice is deployed in the GW-C device, the GW-U device does not need tobe modified, allowing the GW-C device and the GW-U device toindependently evolve.

Embodiment 5

This embodiment of the present disclosure provides another GW-C device90. As shown in FIG. 9, GW-C device 90 includes a processor 91, acommunications interface 92, a memory 93, and a communications bus 94.Processor 91, communications interface 92, and memory 93 communicatewith each other using communications bus 94.

Processor 91 may be a multi-core central processing unit (CPU) or anapplication-specific integrated circuit (ASIC), or is configured as oneor more integrated circuits implementing this embodiment of the presentdisclosure.

Memory 93 is configured to store program code, and the program codeincludes a computer operation instruction and a network flow diagram.Memory 93 may include a high-speed random access memory (RAM), or mayinclude a non-volatile memory such as at least one magnetic disk memory.Memory 93 may be a memory array. Memory 93 may be divided into blocks,and the blocks may be combined into a virtual volume according to aspecific rule.

Communications interface 92 is configured to implement a connection andcommunication among these components.

Processor 91 is configured to execute the program code in memory 93, toimplement operations that include performing core network signalinginteraction with a broadcast/multicast service center and a mobilitymanagement entity; sending a forwarding indication message to a gatewayuser plane GW-U device, the forwarding indication message being used toinstruct the GW-U device to process a packet received by the GW-Udevice; and receiving and processing signaling sent by the GW-U deviceaccording to the forwarding indication message, the signaling being sentby the base station to the GW-U device.

Optionally, performing core network signaling interaction with abroadcast/multicast service center and a mobility management entityincludes, in a session establishment procedure, receiving a firstsession start request message sent by the broadcast/multicast servicecenter, the first session start request message being used to establisha bearer between the GW-U device and the broadcast/multicast servicecenter. Performing core network signaling interaction with abroadcast/multicast service center and a mobility management entityfurther includes sending a second session start request message to themobility management entity, the second session start request messagebeing used to establish a bearer between the base station and the GW-Udevice.

Optionally, the GW-U device connects to the broadcast/multicast servicecenter using an SGi-mb interface, and the operations further includeallocating, when a sending manner on the SGi-mb interface is a unicastmanner, a destination UDP port corresponding to the SGi-mb interface.

Optionally, the GW-U device connects to the broadcast/multicast servicecenter using an SGi-mb interface, and the operations further includesending, when a sending manner on the SGi-mb interface is a multicastmanner, a multicast group join instruction message to the GW-U device.The multicast group join instruction message includes a first multicastgroup join request message and is used to instruct the GW-U device tosend the first multicast group join request message to thebroadcast/multicast service center.

Optionally, the GW-U device connects to the base station using an M1interface, and the operations further include allocating an IP multicastaddress of the M1 interface and a tunnel identifier, the IP multicastaddress being used to identify an IP multicast group using the GW-Udevice as a source point.

Optionally, the forwarding indication message includes a firstforwarding rule. The first forwarding rule is a rule used when the GW-Udevice processes the signaling sent by the base station to the GW-Udevice. Receiving and processing signaling sent by the GW-U deviceaccording to the forwarding indication message includes receiving apreprocessed second multicast group join request message sent by theGW-U device. The preprocessed second multicast group join requestmessage is obtained after the GW-U device preprocesses, according to thefirst forwarding rule, a second multicast group join request messagesent by the base station. Receiving and processing signaling sent by theGW-U device according to the forwarding indication message furtherincludes adding, according to the preprocessed second multicast groupjoin request message, the base station into the IP multicast group usingthe GW-U device as the source point.

Optionally, performing core network signaling interaction with abroadcast/multicast service center includes, in a session terminationprocedure, receiving a first session termination request message sent bythe broadcast/multicast service center, the first session terminationrequest message including specified time information; and releasing abearer context at a moment specified by the specified time information.

Optionally, sending a forwarding indication message to a GW-U deviceincludes sending the forwarding indication message to the GW-U device atthe moment specified by the specified time information. The forwardingindication message includes a rule deletion instruction, so that theGW-U device deletes, according to the rule deletion instruction, asecond forwarding rule used when the GW-U device processes abroadcast/multicast service data packet.

Optionally, performing core network signaling interaction with amobility management entity includes sending a second session terminationrequest message to the mobility management entity. The second sessiontermination request message includes the specified time information, sothat the mobility management entity sends the specified time informationto the base station, and the base station releases the bearer contextaccording to the specified time information.

Optionally, receiving and processing signaling sent by the GW-U deviceaccording to the forwarding indication message includes receiving apreprocessed first multicast group removal request message. Thepreprocessed first multicast group removal request message is obtainedafter the GW-U device preprocesses, according to a first forwardingrule, a first multicast group removal request message sent by the basestation. Receiving and processing signaling sent by the GW-U deviceaccording to the forwarding indication message further includesremoving, according to the preprocessed first multicast group removalrequest message, the base station from the IP multicast group using theGW-U device as the source point.

Optionally, if the sending manner on the SGi-mb interface between thebroadcast/multicast service center and the GW-U device is the multicastmanner, the operations further include sending a multicast group removalinstruction message to the GW-U device. The multicast group removalinstruction message includes a second multicast group removal requestmessage and is used to instruct the GW-U device to send the secondmulticast group removal request message to the broadcast/multicastservice center. The second multicast group removal request message isused to instruct the broadcast/multicast service center to remove theGW-U device from an IP multicast group using the broadcast/multicastservice center as a source point.

Embodiment 6

This embodiment of the present disclosure provides an eMBMS systemmanagement method, applied to a GW-U device. As shown in FIG. 10, themethod includes the following steps:

S1001. The GW-U device receives a forwarding indication message sent bya GW-C device, where the forwarding indication message is used toinstruct the GW-U device to process a packet received by the GW-Udevice.

S1002. The GW-U device receives signaling sent by a base station andsends the signaling to the GW-C device according to the forwardingindication message.

S1003. In a data transmission procedure, the GW-U device receives abroadcast/multicast service data packet sent by a broadcast/multicastservice center and sends the broadcast/multicast service data packet tothe base station according to the forwarding indication message.

For details, refer to Embodiment 1. The base station, thebroadcast/multicast service center, and the gateway control plane devicein the eMBMS system separately connect to the GW-U device. The eMBMSsystem management method provided in this embodiment of the presentdisclosure mainly relates to a method for interacting with the basestation, the broadcast/multicast service center, and the GW-C device bythe GW-U device, so as to establish a session, transmit data, andterminate a session. The following describes step S1001 to step S1003 indetail.

Optionally, the GW-U device connects to the broadcast/multicast servicecenter using an SGi-mb interface, and in a session establishmentprocedure, the method further includes, when a sending manner on theSGi-mb interface is a multicast manner, receiving by the GW-U device amulticast group join instruction message sent by the GW-C device to theGW-U device, the multicast group join instruction message including afirst multicast group join request message; and sending the firstmulticast group join request message to the broadcast/multicast servicecenter, so that the broadcast/multicast service center adds, accordingto the first multicast group join request message, the GW-U device intoan IP multicast group using the broadcast/multicast service center as asource point.

For example, the OpenFlow protocol is used as an interface protocolbetween the GW-U device and the GW-C device. The GW-C deviceencapsulates the first multicast group join request message using theOpenFlow protocol to obtain a Packet-out message, that is, the multicastgroup join instruction message. In this way, after receiving themulticast group join instruction message, the GW-U device obtains thefirst multicast group join request message by means of parsing, andsends the first multicast group join request message to thebroadcast/multicast service center according to an instruction.

Optionally, in the session establishment procedure, the forwardingindication message includes a first forwarding rule, the firstforwarding rule is a rule used when the GW-U device processes thesignaling sent by the base station to the GW-U device, and step S1002includes receiving by the GW-U device a second multicast group joinrequest message sent by the base station, preprocessing the secondmulticast group join request message according to the first forwardingrule, and sending a preprocessed second multicast group join requestmessage to the GW-C device, so that the GW-C device adds, according tothe preprocessed second multicast group join request message, the basestation into an IP multicast group using the GW-U device as a sourcepoint.

For example, a message that is indicated by the first forwarding ruleand is to be forwarded by the GW-U device includes the second multicastgroup join request message that is sent by the base station and used torequest to join the IP multicast group, and indicates that preprocessingto be performed by the GW-U device on the second multicast group joinrequest message is encapsulating the second multicast group join requestmessage using the OpenFlow protocol to obtain a Packet-in message. Thepacket-in message includes a port through which the GW-U device receivesthe first multicast group join request message, and the packet-inmessage is the preprocessed second multicast request message.

Optionally, in the session establishment procedure, the forwardingindication message includes a second forwarding rule. The secondforwarding rule is a rule used when the GW-U device processes the packetsent by the broadcast/multicast service center to the GW-U device. Inthis way, the GW-U device may send the broadcast/multicast service datapacket to the base station according to the second forwarding rule.

For example, the second forwarding rule includes a manner that isindicated by the GW-C device and in which the GW-U device processes thebroadcast/multicast service data packet, and at least one port throughwhich the broadcast/multicast service data packet is output. The atleast one port corresponds to at least one base station in the IPmulticast group using the GW-U device as the source point. In this way,after receiving the broadcast/multicast service data packet, the GW-Udevice processes the broadcast/multicast service data packet accordingto the processing manner of the second forwarding rule, and forwards aprocessed broadcast/multicast service data packet to the correspondingat least one base station using the at least one port.

It may be learned from the foregoing description that, in certainembodiments of the eMBMS system, in the session establishment procedure,related signaling is processed by the GW-U device, and the GW-C devicejust forwards the related signaling and the broadcast/multicast servicedata packet according to an instruction of the GW-C.

Further, in a session termination procedure, the forwarding indicationmessage may include a rule deletion instruction. In this case, themethod may further include deleting, by the GW-U device according to therule deletion instruction, a second forwarding rule used when the GW-Udevice processes the broadcast/multicast service data packet.

Further, in the session termination procedure, step S1002 includesreceiving by the GW-U device a first multicast group removal requestmessage sent by the base station, preprocessing the first multicastgroup removal request message according to a first forwarding rule, andsending a preprocessed first multicast group removal request message tothe GW-C device, such that the GW-C device removes, according to thepreprocessed first multicast group removal request message, the basestation from an IP multicast group using the GW-U device as a sourcepoint.

Optionally, if the sending manner on the SGi-mb interface between thebroadcast/multicast service center and the GW-U device is the multicastmanner, the GW-U device may further receive a multicast group removalinstruction message sent by the GW-C device to the GW-U device. Themulticast group removal instruction message includes a second multicastgroup removal request message. The GW-U may send the second multicastgroup removal request message to the broadcast/multicast service center,the second multicast group removal request message being used toinstruct the broadcast/multicast service center to remove the GW-Udevice from the IP multicast group using the broadcast/multicast servicecenter as the source point.

For example, the multicast group removal instruction message sent by theGW-C device to the GW-U device may be a Packet-out message encapsulatedusing the OpenFlow protocol. The packet-out message may include thesecond multicast group removal request message and a message forwardingindication. In this way, after receiving the multicast group removalinstruction message, the GW-U device sends the second multicast groupremoval request message to the broadcast/multicast service centeraccording to the message forwarding indication.

It may be learned from the foregoing description that, in the sessiontermination procedure, related signaling is processed by the GW-Udevice, and the GW-C device just forwards the related signalingaccording to an instruction of the GW-C.

In this way, behavior of the GW-U device may be controlled by the GW-Cdevice, and the GW-U device just forwards signaling and a data packetaccording to an instruction of the GW-C device. Therefore, after a newfunction is added into or a new service is deployed in the GW-C device,the GW-U device does not need to be modified, allowing the GW-C deviceand the GW-U device to independently evolve.

Embodiment 7

This embodiment of the present disclosure provides a GW-U device 110, soas to implement the eMBMS system management method provided inEmbodiment 6. As shown in FIG. 11, GW-U device 110 includes a firstinteraction unit 111, a second interaction unit 112, and a thirdinteraction unit 113.

First interaction unit 111 is configured to receive a forwardingindication message sent by a GW-C device. The forwarding indicationmessage is used to instruct GW-U device 110 to process a packet receivedby GW-U device 110.

Second interaction unit 112 is configured to receive signaling sent by abase station.

First interaction unit 111 is further configured to send the signalingto the GW-C device according to the forwarding indication message.

Third interaction unit 113 is configured to receive, in a datatransmission procedure, a broadcast/multicast service data packet sentby a broadcast/multicast service center.

Second interaction unit 112 is further configured to send thebroadcast/multicast service data packet to the base station according tothe forwarding indication message.

Optionally, GW-U device 110 connects to the broadcast/multicast servicecenter using an SGi-mb interface. In a session establishment procedure,first interaction unit 111 is further configured to receive, when asending manner on the SGi-mb interface is a multicast manner, amulticast group join instruction message sent by the GW-C device to GW-Udevice 110. The multicast group join instruction message includes afirst multicast group join request message. Third interaction unit 113is further configured to send the first multicast group join requestmessage to the broadcast/multicast service center, so that thebroadcast/multicast service center adds, according to the firstmulticast group join request message, GW-U device 110 into an IPmulticast group using the broadcast/multicast service center as a sourcepoint.

Optionally, in the session establishment procedure, the forwardingindication message may include a first forwarding rule, and the firstforwarding rule is a rule used when GW-U device 110 processes thesignaling sent by the base station to GW-U device 110. Secondinteraction unit 112 is configured to receive a second multicast groupjoin request message sent by the base station. First interaction unit111 is configured to preprocess the second multicast group join requestmessage according to the first forwarding rule and send a preprocessedsecond multicast group join request message to the GW-C device, so thatthe GW-C device adds, according to the preprocessed second multicastgroup join request message, the base station into an IP multicast groupusing GW-U device 110 as a source point.

Optionally, in the session establishment procedure, the forwardingindication message may further include a second forwarding rule, and thesecond forwarding rule is a rule used when GW-U device 110 processes thepacket sent by the broadcast/multicast service center to GW-U device110. The second interaction unit 112 is configured to send thebroadcast/multicast service data packet to the base station according tothe second forwarding rule.

Further, in a session termination procedure, the forwarding indicationmessage may include a rule deletion instruction. Optionally, GW-U 110device further includes a rule deletion unit 114 that is configured todelete, according to the rule deletion instruction, a second forwardingrule used when GW-U device 110 processes the broadcast/multicast servicedata packet.

Optionally, in the session termination procedure, second interactionunit 112 is further configured to receive a first multicast groupremoval request message sent by the base station. First interaction unit111 is further configured to preprocess the first multicast groupremoval request message according to the first forwarding rule and senda preprocessed first multicast group removal request message to the GW-Cdevice, so that the GW-C device removes, according to the preprocessedfirst multicast group removal request message, the base station from anIP multicast group using GW-U 110 device as a source point.

Optionally, if the sending manner on the SGi-mb interface between thebroadcast/multicast service center and GW-U device 110 is the multicastmanner, first interaction unit 111 is further configured to receive amulticast group removal instruction message sent by the GW-C device toGW-U device 110. The multicast group removal instruction messageincludes a second multicast group removal request message. Thirdinteraction unit 113 is further configured to send the second multicastgroup removal request message to the broadcast/multicast service center.The second multicast group removal request message is used to instructthe broadcast/multicast service center to remove GW-U device 110 fromthe IP multicast group using the broadcast/multicast service center asthe source point.

A person skilled in the art would understand that, for the purpose ofconvenience and conciseness, for a specific working process anddescription of the foregoing GW-C device, refer to a correspondingprocess in Embodiment 6.

According to embodiments of GW-U device 110, behavior of GW-U device 110is controlled by the GW-C device, and GW-U device 110 just forwardsreceived signaling and a received data packet according to aninstruction of the GW-C device. Therefore, after a new function is addedinto or a new service is deployed in the GW-C device, GW-U device 110does not need to be modified, allowing the GW-C device and GW-U device110 to independently evolve.

Embodiment 8

This embodiment of the present disclosure provides another GW-U device120. As shown in FIG. 12, GW-U device 120 includes a processor 121, acommunications interface 122, a memory 123, and a communications bus124. Processor 121, communications interface 122, and memory 123communicate with each other using communications bus 124.

Processor 121 may be a multi-core CPU or ASIC, or is configured as oneor more integrated circuits implementing this embodiment of the presentdisclosure.

Memory 123 is configured to store program code, and the program codeincludes a computer operation instruction and a network flow diagram.Memory 123 may include a high-speed RAM, or may include a non-volatilememory such as at least one magnetic disk memory. Memory 123 may be amemory array. Memory 123 may be divided into blocks, and the blocks maybe combined into a virtual volume according to a specific rule.

Communications interface 122 is configured to implement a connection andcommunication among these components.

Processor 121 is configured to execute the program code in memory 123,to implement operations that include receiving a forwarding indicationmessage sent by a GW-C device. The forwarding indication message is usedto instruct GW-U device 120 to process a packet received by GW-U device120. The operations further include receiving signaling sent by a basestation and sending the signaling to the GW-C device according to theforwarding indication message. The operations further include, in a datatransmission procedure, receiving a broadcast/multicast service datapacket sent by a broadcast/multicast service center and sending thebroadcast/multicast service data packet to the base station according tothe forwarding indication message.

Optionally, GW-U device 120 connects to the broadcast/multicast servicecenter using an SGi-mb interface and the operations further includereceiving, when a sending manner on the SGi-mb interface is a multicastmanner, a multicast group join instruction message sent by the GW-Cdevice to GW-U device 120, the multicast group join instruction messageincluding a first multicast group join request message. The operationsfurther include sending the first multicast group join request messageto the broadcast/multicast service center, so that thebroadcast/multicast service center adds, according to the firstmulticast group join request message, GW-U device 120 into an IPmulticast group using the broadcast/multicast service center as a sourcepoint.

Optionally, the forwarding indication message includes a firstforwarding rule that is a rule used when GW-U device 120 processes thesignaling sent by the base station to GW-U device 120. Receivingsignaling sent by a base station and sending the signaling to the GW-Cdevice according to the forwarding indication message includes receivinga second multicast group join request message sent by the base station,preprocessing the second multicast group join request message accordingto the first forwarding rule, and sending a preprocessed secondmulticast group join request message to the GW-C device, so that theGW-C device adds, according to the preprocessed second multicast groupjoin request message, the base station into an IP multicast group usingGW-U device 120 as a source point.

Optionally, the forwarding indication message includes a secondforwarding rule, and the second forwarding rule is a rule used when theGW-U device processes the packet sent by the broadcast/multicast servicecenter to GW-U device 120. Sending the broadcast/multicast service datapacket to the base station according to the forwarding indicationmessage includes sending the broadcast/multicast service data packet tothe base station according to the second forwarding rule.

Optionally, the forwarding indication message includes a rule deletioninstruction and the operations further include deleting, according tothe rule deletion instruction, a second forwarding rule used when GW-Udevice 120 processes the broadcast/multicast service data packet.

Optionally, receiving signaling sent by a base station and sending thesignaling to the GW-C device according to the forwarding indicationmessage includes receiving a first multicast group removal requestmessage sent by the base station, preprocessing the first multicastgroup removal request message according to a first forwarding rule, andsending a preprocessed first multicast group removal request message tothe GW-C device, so that the GW-C device removes, according to thepreprocessed first multicast group removal request message, the basestation from an IP multicast group using GW-U device 120 as a sourcepoint.

Optionally, if the sending manner on the SGi-mb interface between thebroadcast/multicast service center and GW-U device 120 is the multicastmanner, the operations further include receiving a multicast groupremoval instruction message sent by the GW-C device to GW-U device 120,the multicast group removal instruction message including a secondmulticast group removal request message, and sending the secondmulticast group removal request message to the broadcast/multicastservice center. The second multicast group removal request message isused to instruct the broadcast/multicast service center to remove GW-Udevice 120 from the IP multicast group using the broadcast/multicastservice center as the source point.

In the various embodiments described in this application, it should beunderstood that the disclosed system, apparatus, and method may beimplemented in other manners. For example, the described apparatusembodiment is merely an example. As a particular example, the unitdivision is merely logical function division and the actualimplementation may include other divisions. For example, multiple unitsor components may be combined or integrated into another system, or somefeatures may be ignored or not performed. In addition, the displayed ordiscussed mutual couplings or direct couplings or communicationconnections may be implemented using one or more interfaces. Theindirect couplings or communication connections between the apparatusesor units may be implemented in electronic, mechanical, or other forms.

The units described as separate parts may or may not be physicallyseparate, and parts displayed as units may or may not be physical units,may be located in one position, or may be distributed on a plurality ofnetwork units. Some or all of the units may be selected according toactual requirements to achieve the objectives of the solutions of theembodiments.

In addition, functional units in the embodiments of the presentdisclosure may be integrated into one processing unit, or each of theunits may exist alone physically, or two or more units are integratedinto one unit. The integrated unit may be implemented in a form ofhardware, or may be implemented in a form of hardware in addition to asoftware functional unit.

When the foregoing integrated unit is implemented in a form of asoftware functional unit, the integrated unit may be stored in acomputer-readable storage medium. The software functional unit is storedin a storage medium and includes several instructions for instructing acomputer device (which may be a personal computer, a server, or anetwork device) to perform some of the steps of the methods described inthe embodiments of the present disclosure. The foregoing storage mediuminclude may include any medium that can store program code, such as aUSB flash drive, a removable hard disk, a read-only memory (ROM), a RAM,a magnetic disk, or an optical disc.

Although various embodiments of the present disclosure have beendescribed, a person skilled in the art will understand that the presentdisclosure contemplates various changes and modifications to theseembodiments. Therefore, the following claims are intended to beconstrued as to cover the described embodiments and all changes andmodifications falling within the scope of the present disclosure.

A person skilled in the art can make various modifications andvariations to the present disclosure without departing from the spiritand scope of the present disclosure. The present disclosure is intendedto cover these modifications and variations provided that they fallwithin the scope of protection defined by the following claims and theirequivalent technologies.

What is claimed is:
 1. An evolved multimedia broadcast/multicast service (eMBMS) system, comprising: a broadcast/multicast service center; a base station; a mobility management entity configured to connect to the base station; a gateway control plane (GW-C) device configured to connect to the mobility management entity and the broadcast/multicast service center; and a gateway user plane (GW-U) device configured to connect to the base station and the broadcast/multicast service center, the GW-C device configured to connect to the GW-U device; wherein: the GW-C device is configured to perform core network signaling interaction with the broadcast/multicast service center and the mobility management entity, and to send a forwarding indication message to the GW-U device, the forwarding indication message for instructing the GW-U device to process a packet received by the GW-U device; the GW-U device is configured to receive signaling from the base station, and to send the signaling to the GW-C device according to the forwarding indication message; the GW-C device is further configured to receive and process the signaling sent by the GW-U device; and the GW-U device is further configured to, in a data transmission procedure, receive a broadcast/multicast service data packet from the broadcast/multicast service center and send the broadcast/multicast service data packet to the base station according to the forwarding indication message.
 2. The eMBMS system according to claim 1, wherein the GW-C device is further configured to: receive, in a session establishment procedure, a first session start request message from the broadcast/multicast service center, the first session start request message for establishment of a bearer between the GW-U device and the broadcast/multicast service center; and send a second session start request message to the mobility management entity, the second session start request message for establishment of a bearer between the base station and the GW-U device.
 3. The eMBMS system according to claim 1, wherein: the GW-U device connects to the broadcast/multicast service center using an SGi-mb interface; and the GW-C device is further configured to allocate, when a sending manner on the SGi-mb interface is a unicast manner, a destination User Datagram Protocol (UDP) port corresponding to the SGi-mb interface.
 4. The eMBMS system according to claim 1, wherein: the GW-U device connects to the broadcast/multicast service center using an SGi-mb interface; the GW-C device is further configured to send, when a sending manner on the SGi-mb interface is a multicast manner, a multicast group join instruction message to the GW-U device, the multicast group join instruction message comprising a first multicast group join request message and for instructing the GW-U device to send the first multicast group join request message to the broadcast/multicast service center; the GW-U device is further configured to send the first multicast group join request message to the broadcast/multicast service center; and the broadcast/multicast service center is configured to add, according to the first multicast group join request message, the GW-U device into an IP multicast group using the broadcast/multicast service center as a source point.
 5. The eMBMS system according to claim 1, wherein: the GW-U device connects to the base station using an M1 interface; and the GW-C device is further configured to allocate an IP multicast address of the M1 interface and a tunnel identifier, the IP multicast address for identifying an IP multicast group using the GW-U device as a source point.
 6. The eMBMS system according to claim 1, wherein: the forwarding indication message comprises a first forwarding rule, the first forwarding rule for processing, by the GW-U device, the signaling sent by the base station to the GW-U device; the GW-U device is further configured to: receive a second multicast group join request message from the base station; preprocess the second multicast group join request message according to the first forwarding rule; and send a preprocessed second multicast group join request message to the GW-C device; and the GW-C device is further configured to add, after receiving the preprocessed second multicast group join request message and according to the preprocessed second multicast group join request message, the base station into an IP multicast group using the GW-U device as the source point.
 7. The eMBMS system according to claim 1, wherein: the forwarding indication message comprises a second forwarding rule, the second forwarding rule for processing, by the GW-U device, the packet sent by the broadcast/multicast service center to the GW-U device; and the GW-U device is further configured, in the data transmission procedure, to: receive the broadcast/multicast service data packet from the broadcast/multicast service center; and send the broadcast/multicast service data packet to the base station according to the second forwarding rule.
 8. The eMBMS system according to claim 1, wherein the GW-C device is further configured to: receive, in a session termination procedure, a first session termination request message from the broadcast/multicast service center, the first session termination request message comprising specified time information; and release a bearer context at a moment specified by the specified time information.
 9. The eMBMS system according to claim 8, wherein: the GW-C device is further configured to send the forwarding indication message to the GW-U device at the moment specified by the specified time information, the forwarding indication message comprising a rule deletion instruction; and the GW-U device is further configured to delete, according to the rule deletion instruction, a second forwarding rule used when the GW-U device processes the broadcast/multicast service data packet.
 10. The eMBMS system according to claim 8, wherein the GW-C device is further configured to send a second session termination request message to the mobility management entity, the second session termination request message comprising the specified time information such that the mobility management entity sends the specified time information to the base station and the base station releases the bearer context according to the specified time information.
 11. The eMBMS system according to claim 8, wherein: the GW-U device is further configured to: receive a first multicast group removal request message from the base station; preprocess the first multicast group removal request message according to a first forwarding rule of the GW-U device; and send a preprocessed first multicast group removal request message to the GW-C device; and the GW-C device is further configured to remove, after receiving the preprocessed first multicast group removal request message and according to the preprocessed first multicast group removal request message, the base station from an IP multicast group using the GW-U device as the source point.
 12. The eMBMS system according to claim 11, wherein: the GW-C device is further configured to send, if the sending manner on the SGi-mb interface between the broadcast/multicast service center and the gateway user plane device is the multicast manner, a multicast group removal instruction message to the GW-U device, the multicast group removal instruction message comprising a second multicast group removal request message and instructing the GW-U device to send the second multicast group removal request message to the broadcast/multicast service center; and the GW-U device is further configured to send the second multicast group removal request message to the broadcast/multicast service center, the second multicast group removal request message instructing the broadcast/multicast service center to remove the GW-U device from an IP multicast group using the broadcast/multicast service center as the source point.
 13. A gateway control plane (GW-C) device, comprising: a transceiver configured to: perform core network signaling interaction with a broadcast/multicast service center; perform core network signaling interaction with a mobility management entity; and send a forwarding indication message to a gateway user plane (GW-U) device, the forwarding indication message for instructing the GW-U device to process a packet received by the GW-U device; and a processor configured to receive and process signaling sent by the GW-U device according to the forwarding indication message, the signaling having been sent by the base station to the GW-U device.
 14. The GW-C device according to claim 13, wherein the transceiver is configured to: receive, in a session establishment procedure, a first session start request message from the broadcast/multicast service center, the first session start request message for establishing a bearer between the GW-U device and the broadcast/multicast service center; and send a second session start request message to the mobility management entity, the second session start request message for establishing a bearer between the base station and the GW-U device.
 15. The GW-C device according to claim 13, wherein: the GW-U device connects to the broadcast/multicast service center using an SGi-mb interface; and the processor is further configured to allocate, when a sending manner on the SGi-mb interface is a unicast manner, a destination User Datagram Protocol (UDP) port corresponding to the SGi-mb interface.
 16. The GW-C device according to claim 13, wherein: the GW-U device connects to the broadcast/multicast service center using an SGi-mb interface; and the transceiver is further configured to send, when a sending manner on the SGi-mb interface is a multicast manner, a multicast group join instruction message to the GW-U device, the multicast group join instruction message comprising a first multicast group join request message and instructing the GW-U device to send the first multicast group join request message to the broadcast/multicast service center.
 17. The GW-C device according to claim 13, wherein: the GW-U device connects to the base station using an M1 interface; and the processor is further configured to allocate an IP multicast address of the M1 interface and a tunnel identifier, the IP multicast address for identifying an IP multicast group using the GW-U device as a source point.
 18. The GW-C device according to claim 13, wherein: the forwarding indication message comprises a first forwarding rule, the first forwarding rule is a rule used when the GW-U device processes the signaling sent by the base station to the GW-U device; the transceiver is further configured to receive a preprocessed second multicast group join request message from the GW-U device, the preprocessed second multicast group join request message obtained after the GW-U device preprocesses, according to the first forwarding rule, a second multicast group join request message sent by the base station; and the processor is further configured to add, according to the preprocessed second multicast group join request message, the base station into an IP multicast group using the GW-U device as the source point.
 19. A gateway user plane (GW-U) device, comprising: a transceiver, configured to: receive a forwarding indication message from a gateway control plane (GW-C) device, the forwarding indication message instructing the GW-U device to process a packet received by the GW-U device; receive signaling from a base station; send the signaling to the GW-C device according to the forwarding indication message; receive, in a data transmission procedure, a broadcast/multicast service data packet from a broadcast/multicast service center; and send the broadcast/multicast service data packet to the base station according to the forwarding indication message.
 20. The GW-U device according to claim 19, wherein: the GW-U device connects to the broadcast/multicast service center using an SGi-mb interface; and the transceiver is further configured to: receive, when a sending manner on the SGi-mb interface is a multicast manner, a multicast group join instruction message from the GW-C device, the multicast group join instruction message comprising a first multicast group join request message; and send the first multicast group join request message to the broadcast/multicast service center, such that the broadcast/multicast service center adds, according to the first multicast group join request message, the GW-U device into an IP multicast group using the broadcast/multicast service center as a source point. 